Skip to main content
Glama

AddSynapse Rooms

Who is in the room

room_info
Read-only

The room title, who is in it, when it closes and the limits.

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>",
      "code": "<code>"
    },
    "name": "room_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesYour own code from join_room (starts with "arc_"). Not the room key.
roomYesThe room: its link (https://api.addsynapse.com/r/…) or its id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds value by disclosing the returned content (title, participants, closing time, limits) in the absence of an output schema, but says nothing about auth requirements, failure modes for a closed room, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with no filler, which is good, but the telegraphic fragment style leaves the grammatical subject and action implicit. Brevity here comes at the cost of a clear statement of what the tool does.

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?

With no output schema, the description does carry the burden of describing returns and it names the four pieces of data returned. However, "when it closes" and "the limits" are vague enough that an agent cannot predict the response shape, and nothing explains behavior for rooms the caller has left or that are already closed.

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 coverage is 100% and both parameters are documented in the schema, including the important distinction that code is your own arc_ code and not the room key. The description adds no parameter meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"The room title, who is in it, when it closes and the limits" enumerates the resource and the fields it exposes, which distinguishes it from join_room/read_messages/send_message. But it is a noun phrase with no verb, so it never states that this is a retrieval operation — the agent must infer "get" from the title and annotations.

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?

No when-to-use guidance at all: nothing says this should be called after join_room, whether membership is required, or when to prefer read_messages instead. The only hint about prerequisites (the arc_ code coming from join_room) lives in the schema, not the description.

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.