Skip to main content
Glama

hermes_send

Send a message through Hermes to a chat platform like Telegram or Discord by specifying the target chat and message text.

Instructions

Send a message through Hermes to a chat platform (Telegram, Discord, etc.)

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": {
      "target": "<target>",
      "message": "<message>"
    },
    "name": "hermes_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesTarget platform:chat_id (e.g. telegram:6616375428)
messageYesMessage text to send

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, yet it discloses nothing about side effects, delivery guarantees, failure modes, or whether the message is irreversible once sent to the external platform. For an outbound-messaging tool this is a meaningful gap, since an agent cannot tell whether a failed call should be retried, which could duplicate a message.

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 filler, and the action is stated before the qualifiers. Brevity here is efficient rather than padded, though the same space could have carried the missing usage and behavior context.

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?

There is no output schema and no annotations, so the description is the only source of truth, and it says nothing about what a successful call returns (message id, delivery status) or how errors surface. For a two-required-parameter external-send tool, that leaves the agent unable to interpret results or retry safely.

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, making 3 the baseline. The description adds only the platform examples already implied by the schema's target format ("telegram:6616375428") and contributes no additional syntax or constraint detail.

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 gives a concrete verb and resource ("Send a message") plus the transport ("through Hermes") and the destination class ("a chat platform (Telegram, Discord, etc.)"), so an agent knows exactly what the tool does. It falls short of a 5 because it never distinguishes this delivery action from the sibling ask_hermes, which an agent may reasonably confuse with sending a message.

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 statement of when to use this tool rather than ask_hermes, hermes_channels, or coco_health, and no prerequisites or exclusions are given. The only implied guidance is the platform examples in parentheses, which describe the target field, not the usage context.

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