Skip to main content
Glama

remove_coach_location_assignment

Destructive

Unassign a coach from a location within the organization (confirm-gated). Does not remove them from the organization itself — use remove_coach_from_organization for that.

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>",
      "coachId": "<coachId>",
      "locationId": "<locationId>"
    },
    "name": "remove_coach_location_assignment"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 mutation profile is known. The description adds real value beyond that by disclosing the confirm-gate and clarifying the blast radius (location assignment only, not organization membership), though it does not state whether the unassignment is reversible or what a preview returns.

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 waste, with the destructive scope clarification front-loaded before the routing hint. Nothing needs to be cut or reordered.

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 destructive 4-parameter mutation with no output schema, the definition covers purpose, scope boundary, and the confirmation requirement. It stops short of stating idempotency or error behavior on a missing assignment, which would have closed the remaining gap.

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 description coverage is only 25%, but the three required parameters are self-describing identifiers (organizationId, coachId, locationId) and the only non-obvious one, confirm, is documented in the schema itself. The description reinforces the gate with '(confirm-gated)' but adds no format or constraint detail beyond that.

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 ('Unassign a coach from a location within the organization') and immediately distinguishes the scope from the org-level sibling. An agent can tell exactly what this tool does 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 Guidelines5/5

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

Explicitly names the alternative (remove_coach_from_organization) and the condition that selects it — when the intent is only location-level unassignment, not org removal. This is exactly the routing guidance the sibling-heavy context demands.

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.