Skip to main content
Glama

get_organization_role_guide

Read-only

What each built-in gym role (OWNER, ADMIN, PRIMARY_COACH, COACH) is allowed to do.

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": "get_organization_role_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the useful fact that only the four built-in roles are covered (contrasting with custom-role tools), but it says nothing about how the guide is scoped to a specific organization or what form the result takes.

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 short sentence with no filler, efficiently enumerating the covered roles. The lack of a leading verb makes it read as a fragment rather than a definition, which costs a point.

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?

With no output schema, the description should hint at the return shape (a role-to-permissions mapping), which it only loosely implies. Given the tool's low complexity and read-only annotations, the missing pieces are the parameter's meaning and the response structure.

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 0% for the single required parameter, organizationId, and the description never mentions it. An agent must infer that the parameter scopes which organization's role guide is returned, so the description does not compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely — a guide of what each built-in role (OWNER, ADMIN, PRIMARY_COACH, COACH) may do — but it is a noun phrase with no verb, so it does not say whether the tool retrieves, validates, or compares. It partially distinguishes itself from siblings such as get_organization_access and list_organization_custom_roles by scoping to built-in roles only, though this is implied 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 guidance on when to call this versus get_organization_access, list_organization_custom_roles, or assign_organization_member_role. The '(built-in)' scope hints that it does not cover custom roles, but there is no explicit exclusion or usage condition.

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.