Skip to main content
Glama

post

Sends plain-text coordination messages to a specific agent or all agents, enabling project teams to share updates and align on topics.

Instructions

Send a plain-text coordination message to an agent or to everyone.

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": {
      "recipient": "<recipient>",
      "topic": "<topic>",
      "body": "<body>"
    },
    "name": "post"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
topicYes
recipientYesCase-sensitive agent name or *.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already disclose that this is a non-read-only, closed-world operation. The description adds that the message is plain-text and can target a specific agent or everyone, but it does not explain delivery behavior, persistence, notifications, or permissions.

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 definition is a single front-loaded sentence with no wasted wording. It states the action, message type, and audience efficiently.

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

Completeness3/5

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

For a simple three-parameter write tool with annotations and no output schema, the description covers purpose and audience adequately. However, it leaves gaps in usage guidance, topic semantics, and behavioral details such as delivery or persistence.

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

Parameters2/5

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

Schema description coverage is only 33%, with just the recipient parameter documented in the schema. The description reinforces that recipient can be an agent or everyone and calls the body plain-text, but it does not explain the topic parameter or add meaningful semantics for the remaining parameters.

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?

The description states a specific verb ("Send") and resource ("plain-text coordination message") with the target scope ("an agent or to everyone"). It is clear enough for an agent to understand the basic action, but it does not explicitly distinguish this tool from siblings such as ack, inbox, or lock.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no explicit when-to-use guidance, exclusions, or named alternatives. It only implies that this is for sending coordination messages, leaving the agent to infer the selection criteria among sibling tools.

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