Skip to main content
Glama

deactivate_gym_class

Stop a recurring class from running (confirm-gated).

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": {
      "classId": "<classId>"
    },
    "name": "deactivate_gym_class"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only but non-destructive mutation, and the description's 'confirm-gated' note adds useful two-step context. However, the schema's confirm parameter already explains the preview-vs-execute behavior, so the description adds little, and it says nothing about what happens to already-scheduled sessions, enrolled members, or whether the change is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler and the gating caveat placed in parentheses where it is easy to scan. It is efficient, though the terseness borders on under-specification rather than maximizing the few words available.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema and only half the parameters documented in the schema, the description does not cover the consequences an agent needs: effect on future occurrences, existing enrollments, or reversibility. It is enough to identify the operation but not enough to call it confidently against the right sibling.

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 50%: confirm is fully documented inline, while classId has no description. The description implicitly clarifies that classId identifies a recurring class (not a single session), which is modest but genuine added meaning; it offers no format, source, or lookup guidance for the ID.

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 ('stop') and resource ('a recurring class'), so the operation is unmistakable. It does not, however, distinguish itself from nearby siblings like cancel_gym_class_standing or cancel_gym_class_session, which an agent could easily confuse with deactivation.

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 phrase 'stop a recurring class from running'; there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer that this applies to recurring/series classes rather than individual sessions, which is a real ambiguity given the sibling catalog.

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.