Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Tool Search

Tool Search When you have many MCP servers or non core plugin tools attached to a session, their JSON schemas can consume a substantial fraction of the context

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/tool-search

Tool Search When you have many MCP servers or non core plugin tools attached to a session, their JSON schemas can consume a substantial fraction of the context

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. How it works
  2. When does it activate?
  3. Configuration
  4. When NOT to use it
  5. Trade-offs that don't go away
  6. Implementation details
  7. See also

Section map

How it works

Maps how it works to the Core Features documentation path, with the source page reserved for exact commands and updates.

When does it activate?

Maps when does it activate? to the Core Features documentation path, with the source page reserved for exact commands and updates.

Configuration

Maps configuration to the Core Features documentation path, with the source page reserved for exact commands and updates.

When NOT to use it

Maps when not to use it to the Core Features documentation path, with the source page reserved for exact commands and updates.

Trade-offs that don't go away

Maps trade-offs that don't go away to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation details

Maps implementation details to the Core Features documentation path, with the source page reserved for exact commands and updates.

See also

Maps see also to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: How it works, When does it activate?, Configuration, When NOT to use it, Trade-offs that don't go away. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: search, servers, plugin, tools, attached. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for tool search before applying exact upstream commands.

Verify firstHow it works

Open the source anchor for How it works and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for How it works; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for When does it activate? if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page