Skip to main content
Glama

reassign_client_to_coach

Destructive

Move one of an organization's clients from their current coach to a different coach in the same organization (confirm-gated).

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>",
      "profileId": "<profileId>",
      "coachId": "<coachId>"
    },
    "name": "reassign_client_to_coach"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare that this is a destructive, non-read-only operation. The description adds useful context by saying the move is limited to the same organization and is confirm-gated, but it does not explain what happens to the prior coach assignment, whether the change is reversible, or any permission requirements.

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?

The description is a single front-loaded sentence with no unnecessary wording. The purpose and confirm-gated nature are stated efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation tool with four parameters, the description covers the main action, organization scope, and confirmation behavior. However, it leaves out usage alternatives and side-effect details, relying on annotations and the partial schema to fill those gaps.

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%, with only 'confirm' documented. The description partially compensates by mapping organization, client, and coach concepts to the required parameters, but it does not clarify identifier formats or fully document how organizationId, profileId, and coachId are expected to be supplied.

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?

The description states a specific verb and resource: moving a client from their current coach to a different coach within the same organization. It is clear what the tool does, but it does not explicitly differentiate itself from nearby siblings such as offer_ai_coach_to_client or assign_coach_to_location.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives, nor any when-not conditions. The parenthetical 'confirm-gated' signals a two-step execution pattern, but does not explain when a caller should choose reassignment over other coach/client assignment tools.

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.