Skip to main content
Glama

cancel_session

Destructive

Cancel a scheduled session (confirm-gated). Optionally give a short reason the client will see.

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

Input Schema

NameRequiredDescriptionDefault
reasonNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
sessionIdYes

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?

Adds meaningful behavior beyond the annotations: the operation is confirm-gated and returns a preview when confirm is false/omitted, and the reason is visible to the client. That client-visibility disclosure is relevant context the destructiveHint annotation does not convey. It stops short of saying whether cancellation is reversible or what notifications fire.

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, zero filler, with the gating constraint and the optional-parameter hint front-loaded where an agent will read them.

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?

Covers the critical confirm/preview mechanic and reason visibility for a destructive 3-parameter mutation with no output schema. However, it omits permission requirements, side effects on the client's schedule, and whether the cancel can be undone, which matter given no output schema exists to clarify results.

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 only 33% (only confirm is documented in-schema), so the description must compensate. It does explain reason ('short reason the client will see', implying keep it brief and client-facing) and reinforces the confirm gate, but says nothing about sessionId. Partial compensation warrants a middle score.

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+resource: 'Cancel a scheduled session', which is unambiguous about the operation. It does not differentiate itself from siblings such as cancel_gym_class_session or reschedule_session, but the purpose itself is clear.

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 name and the '(confirm-gated)' note; there is no explicit statement of when to cancel versus reschedule, or which sibling cancellation tool applies to which entity type. The preview-then-confirm flow is the only real procedural guidance given.

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.