Skip to main content
Glama

send_message

Sends a chat message to a project group, group, or person (opening a DM if needed), with optional replies and @mentions. The message is verified by reading the chat back.

Instructions

Send a chat message. Teammates see it immediately: confirm wording with the user first unless they dictated it.

to: chat title (project group / group) or a person's name (their DM is opened if it does not exist yet). Or pass dialog_id. reply_to: message id to reply to (from read_chat). mention: people to @mention (names or ids). Newlines are kept. Verified by reading the chat back.

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

Input Schema

NameRequiredDescriptionDefault
toNo
textYes
mentionNo
reply_toNo
dialog_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-idempotent, open-world write, so the description's job is to add context beyond that. It usefully discloses that teammates see the message immediately, that newlines are preserved, that a missing DM is opened as a side effect, and that delivery is verified by reading the chat back. It does not cover permission requirements or whether repeating a send duplicates the message, which matters for a non-idempotent write.

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?

Front-loads the core action and the confirmation rule before the per-parameter notes, and every line carries information. The line-wrapped parenthetical about DM creation is slightly awkward to read but not wasteful.

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?

For a five-parameter mutation tool with an output schema (so return values need not be described), the definition covers addressing, threading, mentions, formatting, and visibility. The remaining gap is operational: no mention of permissions or duplicate-send risk for a non-idempotent call.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and largely does: 'to' explains title vs person name and the DM-creation side effect, 'reply_to' cites its source (read_chat), 'mention' explains names or ids, and dialog_id is named as an alternative. Only 'text' is left implicit, which is reasonable for a required body field.

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?

Specific verb plus resource ('Send a chat message') makes the action unmistakable. It does not explicitly contrast itself with siblings such as edit_message or delete_message, so an agent must infer the boundary from the verb alone.

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 for use: confirm wording with the user first unless they dictated it. It also explains the two addressing routes (title/name vs dialog_id), which is practical selection guidance, but it never states when to prefer this over edit_message or get_project_chat.

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