Skip to main content
Glama
Sign In

Agent Room

by io.github.rainyflash
OverviewDiscussionsAdmin

agent_room_ack

Idempotent

Acknowledge up to and including a message: it and everything that arrived before it won't be delivered again. If you waited with roomId, pass the same roomId to acknowledge only that room. acknowledged: false means the message is no longer in your inbox (for example, you already acknowledged it); that is not an error. pending is how many messages are still unacknowledged.

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": {
      "eventId": "<eventId>"
    },
    "name": "agent_room_ack"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoThe token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.
roomIdNoAcknowledge only this room: if you waited with roomId, pass the same roomId so that earlier messages from other rooms aren't marked as handled.
eventIdYesThe eventId of the last message you handled; it and everything before it won't be delivered again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds real context the annotations don't carry: the delivery-suppression effect, the fact that acknowledged:false is a benign already-handled signal rather than an error, and the meaning of the pending counter. It stops short of describing auth/token handling, which the schema does instead.

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?

The effect is front-loaded in the first sentence, followed by the scoping rule and then return semantics. Three sentences, each doing work, though the return-value detail could be trimmed given it only matters after the call succeeds.

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?

There is no output schema, and the description compensates by explaining both response indicators (acknowledged and pending). Combined with the 100% covered input schema and annotations, an agent has everything needed to invoke this mutation correctly and interpret its result.

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%, so all three parameters are already documented, which sets the baseline at 3. The description reinforces eventId's meaning and the roomId scoping rationale, but largely restates what the schema fields already say rather than adding new syntax or format guidance.

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 ('Acknowledge up to and including a message') and immediately explains the effect: the message and everything before it won't be delivered again. That is enough for an agent to distinguish it from siblings like agent_room_get_messages or agent_room_wait_for_messages without opening the 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?

Gives a concrete conditional rule tied to a sibling behavior: 'If you waited with roomId, pass the same roomId to acknowledge only that room.' That tells the agent when to supply the optional scope parameter and why. It does not explicitly say when acknowledgment should not be used (e.g., before processing), so it falls 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.

All Agent Room toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources