Skip to main content
Glama

check_out

Destructive

End the visit and invalidate its session token. Call when done.

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": "check_out"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent behavior, so the description need not re-state safety. It does add genuinely useful semantics by naming what is destroyed ('invalidate its session token') and tying it to ending the visit. It stops short of saying the invalidation is immediate and unrecoverable, or what a repeat call returns.

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 short sentences, front-loaded with the effect and followed by the trigger. Nothing is redundant and nothing is buried.

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 one-parameter destructive tool, the description plus annotations cover the essentials, but it leaves out whether the session can be reused afterward, what happens on a second checkout call, and how this differs from revoke_sessions. These are reasonable gaps to close for a destructive, non-idempotent operation.

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 'session' parameter is fully documented in the schema, including its expected format and a warning not to put it in a URL. The description adds nothing about the parameter, so the 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?

The description gives a specific verb phrase ('End the visit') and states the concrete effect ('invalidate its session token'), which is far more than a restated name. It is distinguishable from check_in as the terminal counterpart, but it does not differentiate itself from the sibling revoke_sessions, which appears to overlap.

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?

'Call when done' gives only an implied trigger and offers no exclusions, prerequisites, or alternatives such as revoke_sessions. An agent can infer the basic timing but gets no guidance on choosing between this and the session-revocation sibling.

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