Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Search Permissions

search_permissions
Read-only

Search for Microsoft Graph permissions by keyword.

Instructions

Search for Microsoft Graph permissions by keyword.

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": {
      "search_term": "<search_term>"
    },
    "name": "search_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_termYes
permission_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description is consistent with that. However, beyond restating that it is a search, it adds no behavioral context such as matching behavior, rate limits, result ordering, or auth requirements.

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?

It is a single, front-loaded sentence with no wasted words. The brevity is appropriate; the missing details are a completeness issue rather than a conciseness problem.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although an output schema exists and need not be explained, the input schema has two fields at 0% description coverage. The description omits the 'permission_type' filter and gives no selection guidance against the many related permission tools, so it is not complete enough for confident invocation.

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%, so the description must compensate for both parameters. It only hints at 'search_term' through the phrase 'by keyword' and says nothing about 'permission_type', leaving the optional type filter entirely undocumented.

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 states a clear verb ('Search') and resource ('Microsoft Graph permissions') with the keyword-based mechanism, so an agent knows exactly what the tool does. It does not explicitly differentiate itself from siblings such as get_all_graph_permissions or suggest_permissions_for_task, but the keyword-search framing implies the distinction reasonably well.

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?

The description gives no when-to-use guidance, no exclusions, and no named alternatives. It does not explain whether to use this instead of get_all_graph_permissions, suggest_permissions_for_task, or list_permission_categories_and_tasks, leaving the agent to infer selection criteria.

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