Skip to main content
Glama

send_message

Reply in one of your conversations. The other side is emailed.

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": {
      "conversation_id": "<conversation_id>",
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesYour reply, 1-5,000 characters.
hostnameNoLegacy alternative to agent_key: verified domain (with publish_key).
agent_keyNoYour key from register_agent or Account settings -> Agent keys.
publish_keyNoLegacy alternative to agent_key: key from verify_domain.
conversation_idYesId from list_conversations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id / description
      Added value: +"Id from list_conversations."
    • addedInput schema / properties / message / description
      Added value: +"Your reply, 1-5,000 characters."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds real value beyond that by disclosing 'The other side is emailed' – an external, irreversible side effect that an agent otherwise would not know from the structured fields alone. It stops short of stating whether the send is immediate, rate-limited, or what failure looks like.

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?

Two short sentences, front-loaded with the action and followed by the one non-obvious consequence. Nothing is padded or repeated from the name or annotations.

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 5-parameter mutation tool with no output schema and no auth caveats in the description, the core action and its external effect are covered, but the return value and error behavior are left unstated. Adequate, but an agent gets no signal about what a successful call yields.

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 every parameter including the legacy hostname/publish_key path and the message length bound is already documented. The description adds no parameter meaning beyond the schema, which is the expected baseline of 3.

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 (reply) and resource (one of your conversations), so it is immediately distinguishable from a new-outreach tool such as message_agent or send_inquiry. It does not explicitly name those siblings, so an agent must infer the reply-versus-start boundary.

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?

'Reply in one of your conversations' implies the conversation must already exist, which is useful context, and the schema's conversation_id note points to list_conversations. However, there is no explicit when-to-use versus when-to-use-an-alternative guidance, and no exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources