Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get Service Principal By Id

get_service_principal_by_id
Read-only

Get a specific service principal by its object ID.

Instructions

Get a specific service principal by its object ID.

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": {
      "sp_id": "<sp_id>"
    },
    "name": "get_service_principal_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
sp_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

readOnlyHint=true already declares the safety profile, and the presence of an output schema means return values need no explanation. The description adds nothing beyond the name itself — no note on behavior for an unknown or malformed ID, and no confirmation that this is a direct single-object lookup rather than a search.

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?

A single front-loaded sentence with zero filler. Nothing is repeated from the title and every word carries meaning.

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?

For a simple one-parameter read with an output schema and readOnlyHint, the definition is minimally sufficient. The main missing piece is how an agent should obtain sp_id, which matters because the only discovery path is the sibling list_service_principals.

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 description coverage is 0%, so the schema does not document sp_id at all. The description partially compensates by identifying it as the service principal's object ID, but does not clarify the expected format (GUID) or distinguish objectId from appId, which is a common confusion for service principals.

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 specific service principal") plus the lookup key (object ID), so the agent knows exactly what it retrieves. It does not differentiate from siblings like list_service_principals or get_application_by_id, leaving the single-vs-list distinction implicit.

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?

The phrase "by its object ID" implies the tool requires a known identifier and is therefore the follow-up to a listing call, but the description never names list_service_principals as the way to obtain one, nor states any exclusions. Usage is inferable rather than stated.

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