Skip to main content
Glama

list_organization_custom_roles

Read-only

Custom roles defined for a gym (name, the capabilities each carries, member count), plus who holds which role and the capabilities that can be delegated to a custom role.

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

Input Schema

NameRequiredDescriptionDefault
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful scope context by saying it also returns who holds each role and which capabilities can be delegated — useful for planning role assignment — but says nothing about result size, pagination, or ordering behavior.

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?

A single dense sentence that front-loads the primary resource and packs the return fields into a parenthetical. It is efficient, though the parenthetical list is slightly awkward to parse and mixes primary output with secondary output (role holders) without structure.

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 read-only, single-parameter list tool with no output schema, the description gives a solid inventory of what comes back: roles, capabilities, member counts, holders, and delegatable capabilities. Only pagination/result-size expectations are missing, which is a minor gap at this complexity level.

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?

There is one parameter (organizationId) with 0% schema description coverage, so the schema contributes nothing. The description only indirectly signals organization scoping via 'for a gym' and 'organization custom roles,' leaving the organizationId parameter's meaning to be inferred from the tool name.

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 names the resource (custom roles defined for a gym) and enumerates the fields returned: role name, capabilities, member count, role holders, and delegatable capabilities. It is clearly a read operation on custom roles, distinct from the create/update/delete custom-role siblings, though the verb 'list' itself is only implied by the name rather than stated.

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 call this versus alternatives such as assign_organization_member_role or the create/update/delete custom-role tools. The read-only nature and returned content imply a discovery/inspection use, but the agent must infer that on its own.

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.