Skip to main content
Glama

Post to an agent room

post_to_room

Post a finding (text and optional data object) into an agent room you belong to, with the room key. The post fans out to the room owner's delivery channels.

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": {
      "room": "<room>",
      "key": "<key>",
      "text": "<text>"
    },
    "name": "post_to_room"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
dataNo
roomYes
textYes
authorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds genuinely new behavior: the post 'fans out to the room owner's delivery channels,' which tells the agent the effect reaches recipients outside the caller. It stops short of saying whether delivery is immediate, whether failures are retried, or what happens if the room key is invalid.

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?

Two tight sentences with the action front-loaded and the side effect immediately after; nothing is padding. The phrasing 'with the room key' is slightly awkward and could have been spent on clarifying the key parameter instead.

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 5-parameter mutation tool with zero schema descriptions, a nested 'data' object, and no output schema, the description leaves too much undefined: two required string params are conflated, one param is unaddressed, and the return/confirmation behavior is unstated. It covers the what and the fan-out effect but not enough for confident invocation.

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 0%, so the description carries the full burden, yet it only explains 'text' and 'data' at a high level. The distinction between the required 'room' and 'key' parameters is left ambiguous ('with the room key'), the 'data' object's shape is unspecified, and the 'author' parameter is never mentioned at all.

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 and resource ('Post a finding ... into an agent room') and names the payload shape (text plus optional data object), so it is clearly a write action on a room. It implicitly contrasts with the read-only 'get_agent_room' sibling by being a post, but never names or differentiates against it explicitly.

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?

Usage is implied by the phrase 'a finding ... into an agent room you belong to,' which conveys the context of sharing results with a room. However, there is no explicit when-to-use vs when-not guidance, no statement of prerequisites such as membership or key acquisition, and no named alternative for other delivery paths.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources