Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Suggest Permissions For Task

suggest_permissions_for_task
Read-only

Suggest Microsoft Graph permissions for a specific task based on common mappings.

Instructions

Suggest Microsoft Graph permissions for a specific task based on common mappings.

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": {
      "task_category": "<task_category>",
      "task_name": "<task_name>"
    },
    "name": "suggest_permissions_for_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_nameYes
task_categoryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The phrase 'based on common mappings' usefully signals that results are heuristic suggestions rather than authoritative OAuth validation, but the description does not elaborate on completeness, confidence, or how mappings are sourced.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity contributes to the parameter and usage gaps noted elsewhere.

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?

The output schema covers return values and annotations cover safety, but with 0% parameter schema coverage the description should explain what task_name and task_category mean. It also omits that task_category likely derives from list_permission_categories_and_tasks, leaving a key input undefined.

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% and both required parameters lack descriptions. The description mentions 'a specific task,' which loosely maps to task_name, but task_category is never explained, nor are acceptable values or the relationship between the two parameters.

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?

States a specific verb ('Suggest') and resource ('Microsoft Graph permissions') scoped to 'a specific task based on common mappings.' This is clearly distinct from sibling tools like search_permissions or get_all_graph_permissions, though the description does not explicitly name those alternatives.

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?

No guidance on when to use this versus search_permissions, get_all_graph_permissions, or list_permission_categories_and_tasks. It also gives no exclusions or prerequisites, leaving the agent to infer the workflow context entirely.

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