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.

Display what an MCP server exposes: its tools, prompts, and resources, along with their input/output schemas and descriptions. This is what MCP clients see when they connect to the server.

​
Synopsis

tool info [tool] [-m <method>]... [--input] [--output] [-d]
          [--tools] [--prompts] [--resources] [-a] [--json]
          [-k KEY=VALUE]... [--config-file <path>] [--no-save] [-y] [-v] [-L <depth>]

​
Options

​
tool
string
Tool reference (namespace/name) or local path to inspect. Defaults to . (current directory).
​
-m / --method
string
Focus on one or more specific methods by name. Repeatable. When omitted, all methods are shown.
​
--input
boolean
Show only the input schema for the selected method(s). Requires -m.
​
--output
boolean
Show only the output schema for the selected method(s). Requires -m.
​
-d / --description
boolean
Show only the description for the selected method(s) or the tool overall.
​
--tools
boolean
Show only the tool’s MCP tools (callable functions).
​
--prompts
boolean
Show only the tool’s MCP prompts.
​
--resources
boolean
Show only the tool’s MCP resources.
​
-a / --all
boolean
Show all capabilities: tools, prompts, and resources together.
​
--json
boolean
Output the result as JSON. Useful for scripting and agent workflows.
​
-k / --config
string
Runtime configuration value as KEY=VALUE (e.g., API keys). Repeatable. Required by some tools before they can report their capabilities.
​
--config-file
string
Path to a JSON file containing server configuration values.
​
--no-save
boolean
Do not persist config values for future use.
​
-y / --yes
boolean
Skip all interactive prompts. If required config is missing, the command exits with an error.
​
-v / --verbose
boolean
Show verbose output.
​
-L / --level
number
Maximum depth for expanding nested types in schemas. Default: 3. Increase for deeply nested output schemas.

​
Examples

# Inspect tool in current directory
tool info

# Inspect an installed tool
tool info appcypher/bash

# Concise output
tool info appcypher/bash -c

# Show details for a specific method
tool info . -m exec

# Show details for multiple methods
tool info . -m exec -m read

# Show only the input schema for a method
tool info . -m exec --input

# Show only the output schema for a method
tool info . -m exec --output

# Show only the description for a method
tool info . -m exec -d

# List tools only
tool info . --tools

# List prompts only
tool info . --prompts

# List resources only
tool info . --resources

# Show all capabilities
tool info . -a

# JSON output for parsing
tool info . --json

# Pass a config value
tool info . -k API_KEY=xxx

# Expand nested types to depth 5
tool info . -L 5

​
Schema depth

By default, nested object types in schemas are expanded up to 3 levels deep (-L 3). For tools with complex output schemas, increase this value: 
tool info . -m query -L 6
Some tools require configuration (like API keys) before they can start and report their capabilities. Use -k or --config-file to provide those values, or run tool config set <tool> once to save them.

Build docs developers (and LLMs) love

Get started for freeTalk to us