Skip to main content
Glama

cancel_gym_class_session

Destructive

Cancel one dated class session (confirm-gated). Booked members are affected — confirm which session first.

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_gym_class_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.5/5.0
Behavior4/5

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

Beyond the destructive annotation, it warns that booked members are affected and that the operation is confirm-gated. It does not detail whether those members are notified, unbooked, refunded, or otherwise impacted.

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?

The description is two short sentences, front-loads the action, and adds a warning without unnecessary wording. Every phrase contributes to identifying the action or its impact.

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 destructive mutation with no output schema, the description covers the core action and member impact but leaves gaps around the reason parameter, exact side effects on booked members, and return/preview behavior beyond the schema's confirm field.

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

Parameters2/5

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

Schema coverage is only 33%, and the description does not mention the optional reason parameter. It reinforces session selection and confirmation, but the confirmation behavior is already documented in the schema and the description does not compensate for the undocumented parameters.

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 states a specific verb and resource: cancel one dated class session. It implies the distinction from standing/recurring class cancellation through 'one dated,' but it does not explicitly name the relevant sibling or clarify the boundary.

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?

It implies usage by describing the action and advising 'confirm which session first,' which is appropriate for a destructive operation. However, it gives no explicit when-to-use or when-not-to-use guidance versus cancel_gym_class_standing or deactivate_gym_class.

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.