Skip to main content
Glama

leave_organization

Destructive

Leave a gym as a coach (confirm-gated) — high impact: the coach's clients are handed to transferClientCoachId if given. Not for owners (transfer ownership first). Get explicit confirmation before calling with confirm: true.

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": {
      "organizationId": "<organizationId>"
    },
    "name": "leave_organization"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the description earns credit for adding what annotations cannot: the confirm-gated preview behavior, the client-reassignment consequence, and the ownership restriction. The one gap is that it never says what happens to the coach's clients when transferClientCoachId is omitted.

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?

Front-loaded with the verb and resource, then consequences, then the confirmation requirement — an effective order with no filler sentences. The "high impact" label is slightly redundant given the concrete consequences already stated, but it is a single word.

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?

Covers the mutation's safety profile, the preview return behavior (substituting for the absent output schema), and the ownership precondition. The unstated outcome when no transfer coach is supplied is the main remaining ambiguity for a destructive, irreversible-feeling operation.

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?

With only 33% schema coverage, the description must compensate, and it does for two of three parameters: it explains the execute-vs-preview meaning of confirm and the handoff meaning of transferClientCoachId. organizationId is left to the schema, which is acceptable since its meaning is evident.

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 and resource ("Leave a gym as a coach") plus the side effect (clients handed to transferClientCoachId) and an explicit exclusion ("Not for owners"). An agent can distinguish this self-service leave from admin-style sibling operations without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear when-not rule (owners must transfer ownership first) and a procedural prerequisite ("Get explicit confirmation before calling with confirm: true"). It does not name a sibling alternative for the owner case or for admin removal, but the exclusions given are specific and actionable.

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.