hermes-atlas-mcp

Ask Hermes Atlas (free-form RAG)

ask_atlas

Ask natural-language questions about the Hermes Agent ecosystem and get cited answers from repositories, guides, and overview.

Instructions

Ask a free-form natural-language question about the Hermes Agent ecosystem. Delegates to the Hermes Atlas RAG endpoint which searches across repos, summaries, guides, and the ECOSYSTEM.md overview, then returns a cited answer. Good for questions like 'What's the best memory provider for production?' or 'How does Hermes compare to Claude Code?'.

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": {
      "question": "<question>"
    },
    "name": "ask_atlas"
  }
}

Input Schema

Name	Required	Description	Default
`question`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations provided, the description fully discloses the tool's behavior: it delegates to the Hermes Atlas RAG endpoint, searches across specific sources (repos, summaries, guides, ECOSYSTEM.md), and returns a cited answer. This gives the agent a clear mental model of what occurs when invoked.

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 long, front-loaded with the core purpose, and each sentence adds value. The first states what it does, the second gives examples and the return format. No unnecessary filler.

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 single-parameter tool with no output schema, the description is complete. It explains the input, the process, the sources searched, and the output (cited answer), making it sufficient for an agent to decide when and how to use it.

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 input schema only defines 'question' as a string with no description. The description compensates by explaining the parameter's purpose ('free-form natural-language question') and supplying example questions that illustrate the expected format and content.

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 opens with a specific verb and resource: 'Ask a free-form natural-language question about the Hermes Agent ecosystem.' It further distinguishes itself by mentioning the RAG endpoint and cited answers, clearly separating it from sibling tools like search_projects or get_guide.

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 by stating it is for free-form natural-language questions and gives two concrete examples. However, it does not explicitly exclude sibling tools or state when to prefer alternatives, only implying usage through the question format.

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

Deploy Server