Skip to main content
Glama

ask_hermes

Send prompts to Hermes Agent and receive responses; continue multi-turn conversations by reusing a session key.

Instructions

Send a prompt to Hermes Agent and get its response. Supports multi-turn via session_key.

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": {
      "prompt": "<prompt>"
    },
    "name": "ask_hermes"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesThe prompt/message to send
session_keyNoPrevious session key to continue (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, yet it says nothing about the agent's side effects or capabilities, whether calls are synchronous and how long they may take, whether a session persists or expires, or what form the 'response' takes. The word 'response' is the only hint at return behavior.

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

Conciseness4/5

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

Two sentences, front-loaded with the core action, and no filler. It is efficient, though arguably undersized given the tool invokes an autonomous agent, leaving no room for the operational context that actually matters.

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

Completeness2/5

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

For a tool that delegates to an autonomous agent with no annotations and no output schema, the definition omits key facts: latency and synchronous behavior, whether the agent can take actions with side effects, session lifetime, and how errors surface. An agent could call it, but cannot predict its consequences.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented in the input schema. The description adds only mild reinforcement that session_key is for continuing a prior exchange; it gives no guidance on lifespan, reuse, or behavior when an invalid or expired key is supplied. Baseline 3 is appropriate.

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

Purpose4/5

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

The description uses a specific verb and resource: send a prompt to Hermes Agent and get its response. That is unambiguous about what the tool does. However, it offers no differentiation from siblings such as hermes_send (likely messaging) or hermes_channels, so an agent cannot tell from this text alone which of them applies to a given request.

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

Usage Guidelines3/5

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

'Supports multi-turn via session_key' implies the usage pattern for continuing a conversation, which is genuinely useful context. But there is no explicit when-to-use or when-not-to-use guidance, no mention of how this differs from hermes_send, and no statement of prerequisites or cost/latency expectations.

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

Deploy Server

Other Tools