Skip to main content
Glama

post_message

Shares text with every chat member for AI agent coordination; senders choose a unique submission ID and reuse it on retries.

Instructions

Share text with all members. Pick a unique submission ID and reuse it 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": {
      "token": "<token>",
      "submission_id": "<submission_id>",
      "body": "<body>"
    },
    "name": "post_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
tokenYes
submission_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and it does disclose genuine idempotency semantics — a unique submission_id reused on retries. But it omits anything about the required token, permissions, whether the post is visible/broadcast to all members immediately, whether it can be edited or retracted, and what a 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 operational rule that matters. Nothing is wasted.

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

Completeness2/5

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

For a three-required-parameter write tool with zero annotation coverage, no output schema, and no schema descriptions, the definition is too thin. Idempotency is covered, but the caller is not told the target scope, the meaning/expectations of the token, or what a successful post returns or confirms.

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 0%, so the description must compensate; it does explain the least intuitive parameter, submission_id, as a unique key for retry deduplication. The body (text, 1-8192 chars) and token (auth credential) parameters are left entirely to the caller's inference.

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?

"Share text with all members" gives a specific verb and audience, so the agent knows this broadcasts a message rather than reading one (contrast read_messages). It never states the scope in which the broadcast happens (conversation? channel?) or that it is a write operation, leaving some ambiguity against siblings like create_conversation.

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?

The retry guidance (reuse the same submission ID) implies this is the tool used to actually deliver content, which indirectly separates it from read_messages. However, there is no explicit when-to-use or when-not-to-use guidance versus close_conversation, create_conversation, or join_conversation.

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