Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Create Service Principal

create_service_principal

Create a new service principal.

Instructions

Create a new service principal.

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_data": "<sp_data>"
    },
    "name": "create_service_principal"
  }
}

Input Schema

NameRequiredDescriptionDefault
sp_dataYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare this is a non-readonly, non-destructive mutation, so safety basics are covered. The description adds nothing beyond that: it doesn't say what permissions are required, what happens on duplicate service principals, or what must be supplied in the creation payload.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is efficient with no waste, but at this length it reads as under-specification rather than deliberate brevity, and it is not front-loaded with anything beyond a restatement of the title.

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?

An output schema exists, so return values need not be explained. But for a mutation tool whose only input is an opaque free-form object, the description leaves the agent without the field-level guidance needed to invoke it correctly.

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

Parameters1/5

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

Schema coverage is 0% and the single parameter sp_data is a free-form nested object with additionalProperties=true, meaning the agent has no documented fields to supply. The description does not compensate at all — it never mentions what sp_data should contain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Create a new service principal'), so the basic operation is clear. However, it offers nothing to distinguish it from siblings like create_application or create_group, and gives no scope or prerequisite detail.

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 create_application or other create siblings, nor any prerequisites. The agent must infer everything from the name alone.

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