Skip to main content
Glama

assign_organization_member_role

Give a gym member a custom role, or clear it by omitting roleId (confirm-gated). Owner or admin — an access-control change, so confirm exactly which member and role first.

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>",
      "memberUserId": "<memberUserId>"
    },
    "name": "assign_organization_member_role"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, and the schema already documents the confirm-preview behavior. The description adds real value by disclosing the authorization requirement (owner/admin) and that omitting roleId clears the role, which are not in the structured fields. It still does not say what the preview contains or whether a non-existent roleId fails, so the addition is useful but partial.

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 compact sentences with the primary action and the clearing variant front-loaded, then the prerequisite and safety note. No filler, and every clause carries operational meaning.

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 no output schema and only 25% schema coverage, the description covers the critical pieces (authorization, confirm gating, clearing semantics) but omits what the preview or success response looks like and how invalid roleIds are handled. Adequate to call safely, not fully complete.

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%, so the description must compensate: it explains that omitting roleId clears the role and reinforces the confirm gate. However, memberUserId and organizationId are left entirely to their names, and nothing says whether roleId must reference an existing custom role.

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 ('Give a gym member a custom role') and also covers the inverse operation ('clear it by omitting roleId'), which no sibling name implies. It is clearly distinguished from role-definition tools like create_organization_custom_role, though it never names an alternative explicitly.

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 the prerequisite ('Owner or admin') and the caution to 'confirm exactly which member and role first', which tells the agent when this is appropriate and how carefully to act. It stops short of naming when to use this versus a different assignment tool or how to look up a valid roleId.

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.