Skip to main content
Glama

assign_coach_to_location

Assign or move a coach to a location within the organization, with a role there (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>",
      "coachId": "<coachId>",
      "locationId": "<locationId>",
      "role": "<role>"
    },
    "name": "assign_coach_to_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
coachIdYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
locationIdYes
makePrimaryNo
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?

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation. The description adds the useful 'confirm-gated' trait (two-phase preview/execute) and that it may *move* an existing assignment rather than only create one. It stops short of saying what happens to a prior location assignment or role when moving.

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?

One sentence, front-loaded with the action and resource, with the confirm gate parenthesized at the end. Nothing is wasted, though the compression leaves behavioral detail unstated rather than merely concise.

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 6-parameter mutation tool with no output schema and only 17% schema coverage, the description covers the core action, the scope, and the confirm gate. Gaps remain around `makePrimary`, role enum meaning, and what the preview response contains, which an agent must read from the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% — only `confirm` is documented in the schema. The description names coach, location, organization, and role conceptually but adds no meaning about the role enum values, what `makePrimary` does, or how it interacts with an existing assignment, leaving half the parameters semantically bare.

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 gives a specific verb set ('assign or move'), the resource ('a coach to a location'), and scope ('within the organization'), plus the role qualifier. It does not explicitly name a sibling to distinguish from, such as remove_coach_location_assignment or move_coach_under_gym, so differentiation still needs inference.

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

Usage Guidelines3/5

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

'Assign or move' implies both first-time assignment and relocation of an existing assignment, which is useful implied usage. However, there is no explicit statement of when to prefer this over remove_coach_location_assignment, reassign_client_to_coach, or move_coach_under_gym, and no prerequisites are mentioned.

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.