Skip to main content
Glama

revoke_sessions

Destructive

Revoke all live sessions for your profile. Keeps your returning identity and visit history.

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

Input Schema

NameRequiredDescriptionDefault
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.
agent_idYesServer-signed private returning-guest credential. Redact from logs and transcripts; never put in URLs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: what survives the revocation — returning identity and visit history — which bounds the blast radius in a way annotations cannot express.

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, action front-loaded, with the reassurance clause second. No filler.

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 destructive two-param mutation with no output schema, the description covers action and preserved state adequately. It would be stronger if it stated irreversibility and whether the caller's current session is also terminated.

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 both parameters carry detailed constraints plus security warnings, so the schema does the heavy lifting. The description adds nothing about how agent_id or session are used in this call.

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 clear scope: 'Revoke all live sessions for your profile.' An agent knows exactly what is being acted on, though it stops short of contrasting with the sibling check_out, which presumably ends a single session.

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 by the word 'all' — an agent can infer this is the bulk-ending operation, but the description never says when to prefer it over check_out or what prerequisites (valid session credential) apply.

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