Skip to main content
Glama

Leave the world

world_leave

Step out of the world and end the session token.

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": {
      "session": "<session>"
    },
    "name": "world_leave"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYesThe session token world_enter returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The description adds real information beyond the annotations: it discloses that the session token is consumed/terminated, which is the key side effect an agent needs. However, with openWorldHint=true and idempotentHint=false already declared, it never explains the consequence of a second call, what error an expired token produces, or whether the session becomes unusable for subsequent sibling calls.

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?

One short sentence with the action and its effect front-loaded; nothing is padded or repeated. It is appropriately sized for a single-parameter session tool.

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?

For a simple one-parameter tool with full schema coverage and annotations carrying the safety profile, the essentials are present. Still missing is what an agent should expect on failure (already-ended or invalid token) and whether leaving affects any state beyond the token, which matters given idempotentHint=false.

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 schema already documents the single parameter, including its format pattern and its provenance ("The session token world_enter returned"). The description only restates that the token is what gets ended, adding no format, source, or validation detail beyond the schema.

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?

The description names a specific action ("step out") and its consequence ("end the session token"), which clearly identifies this as the session-teardown counterpart to world_enter. It does not explicitly name world_enter as the inverse operation, but the paired semantics are recoverable from the description plus the schema's note that the token comes from world_enter.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this when finished with the world session, since ending the token is described. There is no explicit when-not guidance, no mention of what happens to other in-flight calls, and no statement about calling it after a failed or expired session.

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.

Resources