Skip to main content
Glama

Get role details

get_role
Read-onlyIdempotent

Full details for one role: description, privilege tier, permissions, the admin tasks it covers, its Microsoft Learn page and its RBAC Map page.

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

Input Schema

NameRequiredDescriptionDefault
idYesRole id from search_roles, e.g. "entra-helpdesk-admin".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description adds genuine value beyond them by disclosing the returned content fields, which matters because there is no output schema. It omits behavior for invalid or unknown ids, hence 4 rather than 5.

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?

One tightly packed sentence, front-loaded with the scope ('Full details for one role') followed by the payload fields. Zero filler, no repetition of annotations or schema.

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 one-parameter read tool with no output schema, the description carries the burden of explaining return content and does so by listing the fields. Only minor gaps remain, such as what happens with an unknown id or how 'privilege tier' is expressed.

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 100% and the single 'id' parameter already documents its origin ('Role id from search_roles') and format example in the schema. The description adds no further meaning about the id, so 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 names a specific verb+resource ('Full details for one role') and enumerates exactly what is returned: description, privilege tier, permissions, admin tasks, Learn page, RBAC Map page. This makes it clearly a single-role detail lookup, distinguishable in spirit from search_roles/compare_roles, but it never explicitly names or contrasts a sibling, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: 'for one role' signals a single-record fetch, and the schema hints at following up on an id from search_roles. The description itself offers no explicit when-to-use, when-not-to-use, or alternate-tool routing (e.g. compare_roles for multi-role comparison).

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