Skip to main content
Glama

Send a conversation message

send_message
Destructive

Send the message explicitly requested by the user to a specified accessible conversation. Confirm ambiguous destinations or wording before calling. Other conversation members can see it. Preserve requestId on retries.

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": {
      "requestId": "<requestId>",
      "chat": "<chat>",
      "body": "<body>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe exact message text requested by the user for the specified conversation.
chatYesExisting destination conversation, identified by its ID and conversation type.
requestIdYesA unique UUID for this intended action. Reuse it unchanged when retrying the same action.

Output Schema

NameRequiredDescriptionDefault
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the message is visible to other conversation members, ambiguity must be resolved first, and requestId must be reused on retries. It never explains why destructiveHint=true for a plain message send, and the retry-dedupe guidance sits in mild tension with idempotentHint=false, though the schema's requestId wording makes it consistent rather than contradictory.

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?

Four short, front-loaded sentences with no filler; the visibility warning earns its place. "Preserve requestId on retries" partly duplicates the requestId schema description, which is the only redundancy.

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

Completeness4/5

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

Covers all three required parameters, the social consequence of the write, and the retry protocol; with an output schema present, return values need not be explained. Missing only failure-mode context such as what happens when the destination is not accessible or the kind is wrong.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by tying body to the user's exact wording and by reinforcing requestId reuse on retries. The chat destination parameter gets no extra guidance beyond "accessible conversation."

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?

States a concrete verb and resource ("Send the message ... to a specified accessible conversation") plus a scope constraint that only user-requested messages qualify. It does not name read_messages or any other sibling, so the distinction from alternatives is left implicit.

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?

Gives an explicit precondition (only send what the user explicitly requested, e.g. not autonomous outreach) and an instruction to confirm ambiguous destinations or wording before calling. It lacks a named alternative for the read/inspect case, which would have made it a 5.

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.