Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/superradcompany/tool-cli/llms.txt

Use this file to discover all available pages before exploring further.

Invoke a single method on any installed or local MCP tool without needing an AI client. Useful for testing tools, scripting workflows, and building agent pipelines.

​
Synopsis

tool call [tool] -m <method> [-p KEY=VALUE]... [KEY=VALUE]...
          [-k KEY=VALUE]... [--config-file <path>] [--no-save] [-y] [-v] [--json]

​
Options

​
tool
string
Tool reference (namespace/name) or local path. Defaults to . (current directory).
​
-m / --method
string
required
Method name to call. Supports dot shorthand notation (see Method shorthand below).
​
-p / --param
string
Method parameter as KEY=VALUE or KEY=JSON. Repeatable. Use for named parameters.
  • KEY=VALUE — passes a string value
  • KEY={"a":1} — passes a parsed JSON value
​
args
string
Method parameters as trailing positional arguments (KEY=VALUE or KEY=JSON). An alternative to -p for concise invocations.
​
-k / --config
string
Runtime configuration value as KEY=VALUE (e.g., API keys). Repeatable. Distinct from method parameters — these configure the server itself.
​
--config-file
string
Path to a JSON file containing server configuration values. Merged with any -k flags.
​
--no-save
boolean
Do not persist config values for future calls. By default, provided values are saved.
​
-y / --yes
boolean
Skip all interactive prompts. If required config is missing, the command exits with an error.
​
-v / --verbose
boolean
Show verbose output including the full MCP request and response.
​
--json
boolean
Output raw response content without decorations. Suitable for piping to other tools.

​
Examples

# Call a method in the current directory
tool call . -m exec -p command="ls"

# Call a method on an installed tool
tool call bash -m exec -p cmd="pwd"

# Use -p flag for parameters
tool call bash -m exec -p cmd=ls

# Unquoted param value
tool call weather -m get -p loc=NYC

# Pass server config inline
tool call api -m query -k KEY=xxx

# Load server config from file
tool call . -m test --config-file config.json

# Skip interactive prompts
tool call . -m run -y

# Verbose output
tool call . -m debug -v

​
Method shorthand

MCP tools often use toolname__method naming conventions for their exposed functions. tool call supports a . shorthand to avoid typing the full name. 
# Expands to bash__exec
tool call bash -m .exec -p command="ls -la"

# Expands to files__fs__read
tool call files -m .fs.read -p path="/tmp"
The rules are:
  • .method expands to <toolname>__method
  • .ns.method expands to <toolname>__ns__method
Use tool info first to see all available method names for a tool before calling them.

​
JSON output

Pass --json to get the raw result content, stripping all formatting and decorators. This is useful when composing tool call with other shell commands: 
tool call bash -m exec -p command="ls" --json | jq '.[]'

Build docs developers (and LLMs) love

Get started for freeTalk to us