Skip to main content
Glama

hermes_channels

Lists available Hermes messaging channels and platforms, with an optional platform filter, so agents can discover where to send or receive messages.

Instructions

List available Hermes messaging channels/platforms

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hermes_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoOptional platform filter (telegram, discord, etc.)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 behavioral burden. "List" implies a read-only, safe operation, but nothing is said about whether channels are account-scoped or globally visible, whether authentication or a configured Hermes integration is required, or whether the result reflects live platform state versus a static config list.

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?

It is a single front-loaded sentence with no padding or redundancy. It is efficient, though so terse that it borders on under-specification rather than tight, purposeful description.

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

Completeness3/5

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

For a simple tool with one optional parameter, no annotations, and no output schema, the description states the operation but omits what a returned channel entry contains (name, id, platform) and how results are ordered or scoped. That is a real gap given there is no output schema to fall back on, but the low complexity keeps it near minimum viable.

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%, and the single optional "platform" parameter is documented in the schema with examples (telegram, discord). The description never mentions the filter, so it adds no meaning beyond the schema; the baseline of 3 applies when structured data already does the work.

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?

"List available Hermes messaging channels/platforms" gives a specific verb (list) and resource (Hermes messaging channels/platforms), so an agent knows this is a discovery/enumeration tool. It does not, however, distinguish itself from siblings like hermes_send or ask_hermes, leaving the agent to infer that this one only enumerates destinations rather than acting on them.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no preconditions, and no mention of the obvious alternative flow (e.g., call this to discover a channel before using hermes_send). The only cue is the word "available," which implies usage but does not state it.

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