Skip to main content
Glama

Read a Role

get_role
Read-onlyIdempotent

Read a Role with its direct request_ids and app_requests grouped by shared app. Each app includes app_id, slug, name and aligned request_ids and request_names for its current version, sorted by Request name then ID. Apps are sorted by name then ID; empty app_requests is [].

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": {
      "role_id": "<role_id>"
    },
    "name": "get_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
role_idYesRole UUID in this Project

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, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine behavioral value by describing the response shape, grouping semantics, sort order, and the empty-collection serialization ([] rather than null), but says nothing about failure behavior for an unknown role_id or project scoping errors.

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?

Three sentences, front-loaded with the core action and then the return contract; no filler. The telegraphic phrasing ('empty app_requests is []') is compact but borders on cryptic, which keeps it just below a 5.

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?

With no output schema, the description usefully specifies the nested app structure, aligned request_ids/request_names, and both sort orders — exactly what an agent needs to interpret results. The only gap is error/empty-role behavior, which is minor for a simple idempotent read.

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?

The single parameter role_id is fully described in the schema (100% coverage) as a Role UUID in this Project, and the description adds nothing further about it. With one well-documented parameter, the schema carries the load and the baseline 3 applies.

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 opens with a specific verb+resource, 'Read a Role', and immediately clarifies the payload: direct request_ids plus app_requests grouped by shared app. This distinguishes it from list_roles and the mutation siblings (create_role, update_role, delete_role) implicitly through the singular 'Read a Role' framing, 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use statement, and no alternative is named; the agent must infer that this is the single-role lookup sibling to list_roles from the name alone. Only the required role_id hints at the read-one-by-id pattern.

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.

Resources