Skip to main content
Glama

close_organization

Destructive

Close a gym (confirm-gated) — owner only, high impact: unlists its plans and public page and releases its coaches. Blocked while gym-plan subscribers are live. Get explicit, typed-out confirmation of which gym 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": "close_organization"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, and the description goes well beyond: it names the exact downstream effects (plans unlisted, public page removed, coaches released), states an owner-only authorization requirement, and discloses the blocking precondition. This is exactly the extra context a destructive tool needs.

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?

One dense paragraph front-loaded with the action and its impact, followed by the precondition and then the confirmation protocol. No sentence is filler and ordering matches how an agent needs the 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 2-parameter destructive tool with no output schema, the description covers effects, authorization, and the confirm gate. It does not say whether closure is reversible/restorable or what happens to client data, which is the main remaining gap for a high-impact operation.

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?

The schema documents only confirm (50% coverage), leaving organizationId bare. The description partially compensates by implying organizationId selects 'which gym' and should be explicitly confirmed, but it gives no format, source (slug vs id), or lookup hint. Baseline 3 is appropriate.

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?

Specific verb+resource: 'Close a gym', immediately qualified with the concrete effects (unlists plans and public page, releases coaches). The effect list makes it distinguishable from delete_organization_location or cancel_organization_subscription without opening either 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 an explicit precondition ('Blocked while gym-plan subscribers are live') and an explicit call protocol (obtain typed-out confirmation, then call with confirm: true). It stops short of naming the sibling needed to clear the blocker or an alternative to closing, so it is clear context rather than full when/when-not 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.