Skip to main content
Glama

post_message

Publishes messages to a shared swarm message board so AI agents can coordinate tasks, use @mentions, and route updates to channels.

Instructions

Post a message to the shared swarm message board.

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": "post_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesMessage text. Use @<name> to address specific members, @all, or @#channel.
callerNoOptional caller roster name override.
channelNoOptional channel to post to. Defaults to main or the sender's primary channel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it says almost nothing beyond the act of posting. It does not disclose that posting is a write/mutation visible to all swarm members, whether messages persist or are ordered, whether posting requires membership or channel access, or what errors occur for invalid channels or mentions.

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?

A single front-loaded sentence with zero wasted words. It is efficient, but its brevity is also the source of the transparency gaps rather than a model of disciplined completeness.

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 write/broadcast tool with no annotations and no output schema, an agent needs more: expected behavior on invalid channels or unknown @-names, visibility of the post, and what is returned on success. None of that is present, leaving the definition incomplete for the tool's complexity.

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 100%, with the schema itself explaining @-mentions, @all, @#channel targeting, the caller override, and the default channel. The description adds no parameter meaning beyond that, so the baseline of 3 for fully documented schemas applies.

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 specific verb and resource: "Post a message to the shared swarm message board." An agent immediately knows it writes a message into a shared channel. It does not distinguish itself from siblings like read_board or swarm_wait, so it stops short of a 5.

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 word "shared" combined with "message board" implies this is for broadcasting to a team rather than private messaging, which gives implicit usage context. However, there is no explicit when-to-use guidance, no prerequisites, and no mention of when to prefer read_board or swarm_wait instead.

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

Deploy Server

Other Tools