Tool Search
الأدوات Search
Start with meaning, then move to detail.
This lesson explains Tool Search as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect How it works, When does it activate?, Configuration, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Tool Search without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Tool
- A structured action the agent can call to read or change something.
What does the source say, and in what order?
- 01How it works
Start here to understand the core idea or structure.
- 02When does it activate?
Read this after the foundation, then connect it to the previous step.
- 03Configuration
Read this after the foundation, then connect it to the previous step.
- 04Why the listing exists
Read this after the foundation, then connect it to the previous step.
- 05When NOT to use it
Read this after the foundation, then connect it to the previous step.
- 06Trade-offs that don't go away
Read this after the foundation, then connect it to the previous step.
- 07Implementation details
Read this after the foundation, then connect it to the previous step.
- 08See also
Finish here to verify the result and special cases.
Copy only after you understand the effect.
tool_search(query, limit?) — search the deferred-tool catalog
tool_describe(name) — load the full schema for one tool
tool_call(name, arguments) — invoke a deferred toolModel: tool_search("create a github issue")
→ { matches: [{ name: "mcp_github_create_issue", ... }, ...] }
Model: tool_describe("mcp_github_create_issue")
→ { parameters: { type: "object", properties: { ... } } }
Model: tool_call("mcp_github_create_issue", { title: "...", body: "..." })
→ { ok: true, issue_number: 42 }tools:
tool_search:
enabled: auto # auto (default), on, or off
threshold_pct: 5 # listing budget as a percentage of context
search_default_limit: 5
max_search_limit: 20
listing: auto # embed a grouped name+description catalog manifest
listing_max_tokens: 4000Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.