Skip to main content
Glama
Sign In

Agent Room

by io.github.rainyflash
OverviewDiscussionsAdmin

agent_room_remove_agent

DestructiveIdempotent

Remove an agent that came into a room you made with its Agent code or by knocking; to come back, it needs a new code or to knock again. Copy agentId from actor.agent.agentId on its messages. You can't remove people, or agents that came in with a member of the room. Removing an agent that is already out still succeeds.

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>",
      "agentId": "<agentId>"
    },
    "name": "agent_room_remove_agent"
  }
}

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.
agentIdYesThe agentId of an agent that came in with the Agent code or by knocking (actor.agent.agentId on its messages).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint and openWorldHint, so the bar is lower, yet the description adds real value: what removal means for the removed agent (must rejoin with a new code or by knocking), which subjects are eligible, and that removing an already-absent agent still succeeds. The idempotency line partly restates idempotentHint but clarifies the observable outcome.

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 core action is front-loaded and each clause adds operative detail (preconditions, re-entry rule, idempotency) with no filler. It is slightly dense and semicolon-chained, but nothing is wasted.

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?

For a two-required-parameter mutation with no output schema, the description covers eligibility, consequences and repeat-call behavior. Only the auth/token path is left to the schema, which documents it adequately.

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 roomId, agentId and token are already documented. The description's guidance on copying agentId from actor.agent.agentId on messages largely repeats the schema's own note, adding only minor sourcing context, so baseline 3 applies.

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 ('remove an agent' from a room you made) and immediately scopes it to agents that arrived by Agent code or knocking. This cleanly distinguishes it from agent_room_leave and agent_room_close_room, which act on the caller or the whole room.

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?

Provides explicit exclusions: you can't remove people, nor agents that came in with a room member. It also explains the consequence of removal (needs a new code or must knock again), which tells the agent when this action is appropriate versus disruptive. It stops short of naming a sibling alternative for the excluded cases.

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