Skip to main content
Glama

update_organization_coach_role

Change a coach's role within the organization (confirm-gated) — an access-control change, not a display label. Get explicit confirmation from the coach of exactly which member and which new role 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>",
      "role": "<role>"
    },
    "name": "update_organization_coach_role"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety bar is lower; the description nonetheless adds meaningful behavior beyond them — that this is a confirm-gated access-control mutation and that requiring explicit human confirmation is part of the contract. The preview-when-false behavior is also spelled out in the schema's confirm parameter, so that portion is partially duplicative, and nothing is said about consequences such as changing a member's permission scope.

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 core action stated first and the guardrail second. Nothing is repeated from the schema verbatim and every clause carries information.

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 four-parameter mutation with 25% schema coverage and no output schema, the definition covers the confirmation gate well but leaves the role enum semantics and post-call result undescribed. An agent still has to infer what OWNER vs COACH means and whether escalation to OWNER carries extra conditions.

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 only 25% — only confirm is documented — so the description must compensate, and it does so only partially by framing the operation as picking an exact member and an exact new role. It adds no explanation of the four role values (OWNER, ADMIN, PRIMARY_COACH, COACH), their privilege hierarchy, or what organizationId/coachId identifiers are accepted.

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 and resource ('Change a coach's role within the organization') and adds a disambiguating clause — 'an access-control change, not a display label' — that separates it conceptually from label-editing siblings. It stops short of naming the related role tools (update_organization_custom_role, assign_organization_member_role), so differentiation is conceptual rather than explicit.

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?

It states a concrete pre-call prerequisite: obtain explicit confirmation from the coach naming both the exact member and the exact new role before invoking with confirm: true. That is real usage guidance. It does not say when to prefer a sibling (e.g., custom roles vs. built-in roles), so it falls short of full when/when-not/alternative coverage.

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.