Skip to main content
Glama

remove_coach_from_organization

Destructive

Remove a coach from the organization entirely (confirm-gated) — high impact: optionally transfer their clients to another coach in the same call, or their clients are left unassigned. Get explicit confirmation of exactly which coach, and where their clients go, 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>",
      "coachId": "<coachId>"
    },
    "name": "remove_coach_from_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
coachIdYes
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 declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds the genuinely non-obvious consequence: clients are either transferred in the same call or left unassigned. The confirm/preview mechanic is largely duplicated from the schema's confirm field, so it is valuable but not fully net-new.

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?

Two sentences, front-loaded with the verb, scope and impact level, followed by the confirmation requirement. Dense but every clause carries information; the parenthetical '(confirm-gated)' is slightly redundant with the schema's confirm description.

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?

There is no output schema, and the description usefully explains what happens when confirm is false (preview only) and the two possible fates of the coach's clients. For a 4-parameter destructive tool this is close to complete, with only permissions/irreversibility left unstated.

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?

Schema description coverage is only 25% (only confirm is documented), so the description must compensate — and it does for the key ambiguous parameter, explaining that transferClientCoachId moves the removed coach's clients to another coach in the same call. organizationId and coachId are left unannotated but are self-explanatory from their names.

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 with an explicit scope qualifier: 'Remove a coach from the organization entirely'. The word 'entirely' distinguishes this from org-adjacent siblings such as remove_coach_location_assignment (a scoped removal), so an agent can pick it without opening a 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 clear operating context: this is a high-impact, confirm-gated action, and the caller must obtain explicit confirmation of which coach and where clients go before passing confirm: true. It does not explicitly rule out or route to alternatives like reassign_client_to_coach for the pure client-transfer case, which keeps it below a 5.

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.