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.

Search across all installed tool schemas — tool names, descriptions, input/output fields, and parameter names — using a regular expression. Useful for finding which tools support a specific operation, discovering parameter names, and building agent tool-discovery workflows.

​
Synopsis

tool grep <pattern> [tool] [-m <method>] [--input] [--output]
          [-n] [-d] [-i] [-l] [--json] [-L <depth>] [--live]

​
Options

​
pattern
string
required
Regex pattern to search for. Matched against schema field names, descriptions, and values across all installed tools (or a specific tool if provided).
​
tool
string
Limit the search to a specific tool reference (namespace/name) or local path. When omitted, all installed tools are searched.
​
-m / --method
string
Restrict the search to a specific method within the tool.
​
--input
boolean
Search only in input schemas (parameters accepted by methods).
​
--output
boolean
Search only in output schemas (return values of methods).
​
-n / --name
boolean
Search field/key names only. Excludes description text and values.
​
-d / --description
boolean
Search description text only. Excludes field names and values.
​
-i / --ignore-case
boolean
Perform a case-insensitive search.
​
-l / --list
boolean
List only the matching schema paths, without showing their values.
​
--json
boolean
Output results as JSON. Useful for scripting and agent workflows.
​
-L / --level
number
Maximum depth for expanding nested types in output schemas. Default: 3.
​
--live
boolean
Connect to the running MCP server to retrieve schema data instead of using the static manifest. Use this when the manifest may be out of date or the tool generates schemas dynamically.

​
Examples

# Search "file" across all installed tools
tool grep file

# Concise output
tool grep temperature -c

# Regex search in a specific tool
tool grep "read|write" bash

# Search descriptions only
tool grep api_key -d

# Search names/keys only
tool grep path -n

# Search input schemas only
tool grep config --input

# Search output schemas only
tool grep result --output

# Search within a specific method
tool grep database -m query

# Case-insensitive regex
tool grep "^get_" -i

# List matching paths only (no values)
tool grep file -l

# Connect to the live server instead of static manifest
tool grep file --live

​
Use cases

Finding tools that support specific operations Search all installed tools to find which ones expose a particular capability: 
# Which tools have a "read" operation?
tool grep read -n

# Which tools accept a "path" parameter?
tool grep path --input -n
Building agent tool-discovery workflows Pipe JSON output to build dynamic tool selection for AI agents: 
# Find all tools that deal with files, get JSON for the agent
tool grep file --json | jq '.[] | .path'
Narrowing results progressively Combine flags to zero in on what you need: 
# Find "database" only in method inputs of a specific tool
tool grep database -m query --input bash
Use --live when working with tools that generate their schemas dynamically at runtime, as the static manifest may not reflect the full set of available fields.
tool grep searches the static manifest data by default. This is fast and works without starting the server. Use --live only when you specifically need runtime-generated schema data.

Build docs developers (and LLMs) love

Get started for freeTalk to us