Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get Conditional Access Policy By Id

get_conditional_access_policy_by_id
Read-only

Get a single conditional access policy by its ID with comprehensive details.

Instructions

Get a single conditional access policy by its ID with comprehensive details.

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": {
      "policy_id": "<policy_id>"
    },
    "name": "get_conditional_access_policy_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
policy_idYesThe unique identifier (ID) of the conditional access policy.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds only 'with comprehensive details', which hints at return richness but gives no information about failure behavior for an unknown ID or required 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?

One front-loaded sentence with no wasted words. It is efficient, though the trailing 'with comprehensive details' is close to filler.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. For a single-parameter read, the definition is adequate but thin – nothing on error behavior or the relationship to the list tool.

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?

Single parameter with 100% schema description coverage, so the schema fully documents policy_id as the unique identifier. The description adds nothing beyond that; 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?

States a specific verb and resource: 'Get a single conditional access policy by its ID'. The word 'single' contrasts implicitly with the sibling list tool get_conditional_access_policies, but that sibling is never named, so differentiation is left to inference.

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 by 'by its ID' – an agent can infer this is the follow-up call after listing policies, but there is no explicit when-to-use, prerequisite, or reference to get_conditional_access_policies as the alternative.

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