Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Delete Service Principal

delete_service_principal
Destructive

Delete a service principal by its object ID.

Instructions

Delete a 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": "delete_service_principal"
  }
}

Input Schema

NameRequiredDescriptionDefault
sp_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it doesn't say the deletion is irreversible, whether related role assignments/app credentials are cleaned up, or what permissions/consent are required. For a destructive operation this is a meaningful gap.

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 zero filler and the key identifier requirement stated immediately. It is efficient, though its brevity leans toward under-specification for a destructive tool.

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?

Output schema exists and annotations cover the safety flags, and the tool is low-complexity with a single required parameter. Still, for an irreversible destructive action the description should add at least a caution and any permission requirement, which are missing.

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 coverage is 0% and there is one parameter (sp_id) with no type details beyond string. The phrase 'by its object ID' usefully disambiguates that this expects the directory object ID rather than an appId/clientId, which is real added meaning, but format examples or validation expectations are absent.

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 ('Delete') and resource ('service principal') plus the identifier used, which cleanly separates it from siblings like delete_group, delete_application, and update_service_principal. No explicit sibling contrast is offered, but the name-plus-resource pairing leaves no ambiguity about what it does.

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 offers no guidance on when to use this versus alternatives such as update_service_principal or list_service_principals to verify first, and no mention of prerequisites like confirming the object ID. Usage must be inferred from the tool name alone.

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