Skip to main content
Glama

revoke_merchant_session

Revoke one merchant session without disabling the merchant identity or deleting work/payment recovery records. Parent merchant key required.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "revoke_merchant_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does useful work by disclosing what is NOT destroyed (identity, work/payment recovery records) and that a parent merchant key is required, but it omits whether revocation is immediate, irreversible, or idempotent, and what happens to an already-revoked session.

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 tight sentences with zero filler: the action and its boundary first, the prerequisite last. Every clause carries decision-relevant information.

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 single-parameter mutation with no output schema, the definition covers action, blast radius, and the auth prerequisite. The only material omission is reversibility/idempotency behavior of the revocation itself.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but there is only one parameter and its name (sessionId) is self-explanatory, with UUID format enforced in the schema. The description adds the prerequisite that the parent merchant key must accompany the call, which is meaning beyond the schema's single field.

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 (revoke) and resource (one merchant session), and immediately bounds the scope by saying it does not disable the merchant identity or delete work/payment recovery records. This distinguishes it cleanly from broader identity-destroying operations an agent might otherwise reach for.

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?

The scope statement implies when this is the right tool: narrow, single-session revocation rather than merchant deactivation. However, it never names an alternative tool (e.g., a listing tool to find session IDs) or states the inverse condition for those siblings, so the agent must infer routing.

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