Skip to main content
Glama
GHDaru
by GHDaru

mcpmessage_send

Send messages between registered chats with optional structured payload and reply-to threading, enabling direct communication and coordinated responses across chat sessions.

Instructions

Send a message from one registered chat to another.

Besides the text body, 'data' carries structured information (a summary, findings, references) so the receiving chat gets typed content instead of prose to re-parse. To answer a received message, pass its id as 'reply_to': the reply lands in the same thread and the original sender can correlate it.

Args: sender: Registered name of the sending chat. recipient: Registered name of the receiving chat (see mcpmessage_list_chats). body: The message text; cannot be empty. data: Optional JSON-serializable payload shared with the message. reply_to: Optional id of the message being answered.

Returns: JSON of the stored message {id, seq, sender, recipient, body, data, reply_to, thread_id, created_at, read_at}, or an "Error: ..." string (unknown chat, empty body, sender == recipient, unknown reply_to).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
dataNo
senderYes
reply_toNo
recipientYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

A4.8/5.0
Behavior5/5

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

The description goes well beyond the basic annotations by explaining thread behavior, stored message fields, and error cases. It makes the side effects and failure modes clear, which is especially valuable for a non-readOnly, non-idempotent mutation tool.

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?

The description is well-structured with an opening summary, focused paragraphs on data and reply_to, and an Args/Returns layout. It is detailed yet each sentence earns its place and the most important purpose is front-loaded.

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

Completeness5/5

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

The description covers all five parameters, required fields, return shape, and error cases. Despite the lack of schema-level descriptions, an agent has enough information to invoke the tool correctly and interpret the result.

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 description coverage is 0%, but the description compensates fully by explaining every parameter's meaning, validation constraints (non-empty body, registered names), and the optional nature of data and reply_to. This adds substantial meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: sending a message from one registered chat to another. It clearly distinguishes this from sibling tools like list_chats, inbox, and thread by focusing on the act of sending.

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?

The description gives clear usage context, such as using data for structured payloads and passing reply_to to answer a received message. It also directs the agent to mcpmessage_list_chats for recipient names, though it does not explicitly list when not to use the tool.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GHDaru/mcpmessage'

If you have feedback or need assistance with the MCP directory API, please join our Discord server