Hermes BibleUnofficial Docs
← All docs Docs / Developer Guide

Tools Runtime

Hermes tools are self registering functions grouped into toolsets and executed through a central registry/dispatch system. Primary files: Tool registration mode

Developer Guide
Section
Developer Guide
Source
hermesbible.com/docs/developer-guide/tools-runtime

Hermes tools are self registering functions grouped into toolsets and executed through a central registry/dispatch system. Primary files: Tool registration mode

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. Tool registration model
  2. How registry.register() works
  3. Discovery: discover_builtin_tools()
  4. Tool availability checking (check_fn)
  5. Toolset resolution
  6. How get_tool_definitions() filters tools
  7. Legacy toolset names
  8. Dispatch
  9. Dispatch flow: model tool_call → handler execution
  10. Error wrapping
  11. Agent-loop tools
  12. Async bridging
  13. The DANGEROUS_PATTERNS approval flow
  14. Terminal/runtime environments

Section map

Tool registration model

Maps tool registration model to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

How registry.register() works

Maps how registry.register() works to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Discovery: discover_builtin_tools()

Maps discovery: discover_builtin_tools() to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Tool availability checking (check_fn)

Maps tool availability checking (check_fn) to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Toolset resolution

Maps toolset resolution to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

How get_tool_definitions() filters tools

Maps how get_tool_definitions() filters tools to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Legacy toolset names

Maps legacy toolset names to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Dispatch

Maps dispatch to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Developer Guide 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: Tool registration model, How registry.register() works, Discovery: discover_builtin_tools(), Tool availability checking (check_fn), Toolset resolution. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: tools, runtime, registering, functions, grouped. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitDeveloper Guide documentation

Use when you need orientation for tools runtime before applying exact upstream commands.

Verify firstTool registration model

Open the source anchor for Tool registration model 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 Developer Guide, then open the linked source page for exact current syntax.
  2. Start with the source section for Tool registration model; 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 How registry.register() works 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

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

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