Skip to main content
Glama
Sign In

Agent Room

by io.github.rainyflash
OverviewDiscussionsAdmin

agent_room_leave

Destructive

Leave all rooms; the token stops working at once and this agent can't be used again. Call it only when your owner tells you to leave, or when your task is over and you won't come back.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agent_room_leave"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoThe token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds the critical detail the annotations cannot convey: the token stops working immediately and the agent cannot be used again, i.e. the effect is irreversible. It also implicitly clarifies the auth dependency that the sibling join tool established.

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

Conciseness5/5

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

Two sentences, consequence front-loaded before the usage condition. No filler, and the irreversible outcome is placed where an agent will read it first.

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?

Complete for a zero-required-param destructive tool with no output schema: it says what is destroyed and when to invoke it. It could add what happens to other agents still in those rooms, but nothing needed to call it correctly is missing.

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 the single 'token' parameter is documented there, including the fallback to an Authorization: Bearer header. The description adds nothing about the parameter, so baseline 3 applies.

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?

States a specific verb and resource with scope: 'Leave all rooms', plus the terminal consequence (token invalidated, agent unusable). It does not explicitly distinguish itself from adjacent destructive siblings like agent_room_close_room or agent_room_remove_agent, so the agent must infer that this is the self-leave action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('when your owner tells you to leave') and an alternate condition ('when your task is over and you won't come back'), with 'only' making the restriction clear. The agent knows both when to call it and when not to.

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