Skip to main content
Glama

delete_organization_location

Destructive

Permanently delete a location (confirm-gated). Coaches and clients assigned to it are not moved automatically — reassign them 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": {
      "locationId": "<locationId>"
    },
    "name": "delete_organization_location"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description still adds meaningful behavior beyond that: the deletion is permanent, it will NOT cascade-move coaches or clients, and confirm gating produces a preview when not set. It omits permission/authorization requirements and any failure modes for locations still holding assignments.

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 sentences, zero filler, with the destructive nature and the confirm gate front-loaded before the consequence warning. Every clause carries information an agent needs before invoking the tool.

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 two-parameter destructive tool with no output schema, the description covers irreversibility, the preview mechanism, and the side-effect on existing assignments. The main remaining gap is permission requirements and what happens if the caller deletes a location that still has assignments.

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 in the schema, and the description echoes its gating behavior without adding syntax. locationId carries no schema description and the description does not clarify its expected format (raw ID vs slug), leaving that meaning unaddressed by either source.

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 and resource ('Permanently delete a location') and flags the confirm gate, which cleanly separates it from create_organization_location and update_organization_location. No sibling is named explicitly, but the destructive verb makes the distinction unambiguous in practice.

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 hard precondition ('reassign them first') and notes the operation is confirm-gated, which is real when-to-use guidance rather than vague context. It stops short of naming alternatives (e.g. remove_coach_location_assignment) for the reassignment step, so the agent must infer the follow-up path.

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.