hermes-atlas-mcp

Get Hermes Handbook guide page

get_guide

Fetch the full text of Hermes Handbook guide pages by slug: 'hub' for beginner guide, 'install' for installation, 'vs-claude-code' for Claude Code comparison.

Instructions

Fetch the full text of a Hermes Handbook guide page. Args: slug — one of 'hub' (beginner's guide at /guide/), 'install' (/guide/install/), or 'vs-claude-code' (/guide/vs-claude-code/). Any other slug returns an error.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_guide"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 12, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and discloses key behaviors: it returns full text, accepts only three specific slugs, and errors on invalid slugs. It does not mention non-mutability explicitly, but 'fetch' strongly implies a read-only operation, which is sufficient for this tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with the primary purpose stated first, followed by a compact parameter breakdown. Every word contributes value, and the structure is easy to parse for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter fetch tool, the description covers the purpose, accepted inputs, and error behavior completely. The absence of an output schema is mitigated by the phrase 'full text,' which sufficiently conveys the return value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only defines slug as a string with no enum, so the description provides essential semantics by listing the exact allowed values and their corresponding URLs. It also clarifies the error condition for invalid slugs, greatly aiding correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it fetches the full text of a Hermes Handbook guide page, with a specific verb and resource. It enumerates the exact valid slug values, which distinguishes it from sibling tools like get_project and search_projects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for usage by listing all accepted slug values and noting that any other slug returns an error. It does not explicitly mention alternatives, but the allowed values and error behavior make the usage unambiguous for this simple fetch operation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server