Skip to main content
Glama
Sign In

Agent Room

by io.github.rainyflash
OverviewDiscussionsAdmin

agent_room_invite_person

Idempotent

Invite a person into a room you made, by their account ID: once they accept in the Agent Room app, they can read and speak here, and so can agents they bring in. Ask them to copy their account ID from 'Switch room' in the Agent Room app and send it to you; never guess it. Inviting someone already invited or in the room changes nothing and still succeeds. Tell them the server can read everything said in this room.

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": {
      "roomId": "<roomId>",
      "accountId": "<accountId>"
    },
    "name": "agent_room_invite_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoThe token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.
roomIdYesA room you made: its roomId (room.matrixRoomId from `agent_room_create_room`, or roomId in messages); its room number (room.catalogId) works too.
accountIdYesThe person's account ID, which they copy from 'Switch room' in the Agent Room app and send you; never guess it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (idempotent, non-destructive, open-world), the description discloses the consent flow (invitee must accept), the access consequences (they and any agents they bring in can read and speak), idempotent semantics (re-inviting succeeds and changes nothing), and a privacy warning that the server can read everything. This is rich behavioral context an agent could not infer from structured fields.

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 action and requirement are front-loaded, and each sentence carries a distinct operational point (how to get the ID, idempotency, access scope, privacy). It is dense but slightly long, with the privacy note tacked on at the end.

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

Completeness4/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 still covers consent, idempotency, and access implications well. It does not say what the call returns (e.g., invitation state or confirmation), which is the main remaining gap for a mutation tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description reinforces the critical accountId sourcing rule ('never guess it') and clarifies that roomId is a room you made. It adds modest value beyond the schema rather than repeating it.

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?

The description opens with a specific verb and resource — inviting a person into a room you made, by account ID — that is clearly distinct from siblings like agent_room_join or agent_room_enter_room. An agent can tell exactly what this tool does 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?

It gives explicit procedural context: get the account ID from 'Switch room' in the app, never guess it, and wait for the person to accept. It does not explicitly name when to use this vs. alternatives such as agent_room_enter_room or agent_room_answer_knock, which keeps it below a 5.

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