Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get All Graph Permissions

get_all_graph_permissions
Read-only

Get all Microsoft Graph permissions directly from the Microsoft Graph API.

Instructions

Get all Microsoft Graph permissions directly from the Microsoft Graph API.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_all_graph_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes the safety profile. The description adds that permissions are retrieved directly from the Graph API, implying a live, unfiltered fetch. It does not mention pagination, volume, or rate-limit considerations for retrieving all permissions.

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?

It is a single, front-loaded sentence with no wasted clauses. It is slightly redundant in saying "Microsoft Graph permissions directly from the Microsoft Graph API," but remains efficient.

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 an output schema present and no input parameters, the definition covers the basic call mechanics. It is missing sibling differentiation and any note about result size, pagination, or intended use, which would help an agent decide between this and other permission-related tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. There is no parameter behavior to explain, and the schema has no gaps to compensate for.

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 uses a clear verb and resource ("Get all Microsoft Graph permissions") and specifies the source (Microsoft Graph API). However, it does not distinguish this tool from sibling permission tools like search_permissions or list_permission_categories_and_tasks.

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 use this tool versus alternatives such as search_permissions or suggest_permissions_for_task. It only states what the tool does, not the conditions under which it should be chosen.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.