Skip to main content
Glama

Send a chat message

chat_send

Posts a new text message to a flat chat as the signed-in member, notifying other members and anyone mentioned; use it to share updates or ask questions, not to edit existing messages.

Instructions

Posts a new text message to the flat chat as the signed-in member; use chat_edit to change a message you already sent. Notifies the other members, and anyone mentioned gets a separate mention notification, so confirm the wording with the user first. Text only, no images; a blank body gives empty_message. A reply target that is missing or deleted gives reply_to_not_found. Each call creates a new message, so do not retry blindly. Returns the created message, the mentioned member ids and a warning that is null unless the push delivery could not be confirmed.

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": {
      "body": "<body>"
    },
    "name": "chat_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesMessage text, trimmed, up to 4000 characters. Write "@Name" with the exact member name to mention someone.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
mentionMemberIdsNoMember ids to mention, from members_list. A member is only mentioned if body also contains their "@Name"; you cannot mention yourself.
replyToMessageIdNoId of an existing, not deleted message in this flat to reply to, from chat_messages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / body / description
      Added value: +"Message text, trimmed, up to 4000 characters. Write \"@Name\" with the exact member name to mention someone."
    • addedInput schema / properties / mentionMemberIds / description
      Added value: +"Member ids to mention, from members_list. A member is only mentioned if body also contains their \"@Name\"; you cannot mention yourself."
    • addedInput schema / properties / replyToMessageId / description
      Added value: +"Id of an existing, not deleted message in this flat to reply to, from chat_messages."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say this is a non-readonly, non-idempotent, non-destructive write; the description adds the substantive behavior: other members are notified, mentions trigger a separate notification, text only with no images, and the defined error outcomes empty_message and reply_to_not_found. It also explains the returned warning flag for unconfirmed push delivery and warns against blind retries because each call creates a new 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?

Purpose and the chat_edit alternative are front-loaded, then side effects, error codes and return shape follow in a logical order. It is dense but nearly every clause carries operational value; only the notification phrasing is slightly repetitive.

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?

With no output schema, the description still previews the return value (created message, mentioned member ids, nullable push warning) and covers side effects and failure modes. Nothing an agent needs to call this write tool safely is missing.

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, but the description adds meaning the schema does not: a blank body yields empty_message and a missing or deleted reply target yields reply_to_not_found. The mention-notification consequence is noted, though the mention id/body coupling is left mostly to the 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?

States a specific verb and resource ("Posts a new text message to the flat chat as the signed-in member") and immediately names the sibling it is not, chat_edit. An agent can separate send from edit without opening either schema.

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?

Explicitly routes message modification to chat_edit and adds a confirmation-with-user precondition before sending. It gives clear operating context but does not spell out when a member should instead use chat_react or chat_messages, so it stops just short of full when/when-not coverage.

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