Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Update Service Principal

update_service_principal
Destructive

Update an existing service principal.

Instructions

Update an existing 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_id": "<sp_id>",
      "sp_data": "<sp_data>"
    },
    "name": "update_service_principal"
  }
}

Input Schema

NameRequiredDescriptionDefault
sp_idYes
sp_dataYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true, so the description is not required to establish that this mutates state, but it adds nothing beyond the title. It does not say whether sp_data replaces the whole object or patches selected fields, which is a critical distinction for a destructive update, and it does not mention reversibility or permission requirements.

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?

One sentence, front-loaded with the verb and resource, so there is no filler. The brevity here is under-specification rather than efficiency, since removing it all leaves the agent without the payload guidance it needs.

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?

For a destructive mutation taking an opaque nested object, the description should identify at least the common updatable fields. An output schema exists, so return values need not be explained, but the input side remains a black box, leaving the definition incomplete for correct invocation.

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 description coverage is 0%, and the sp_data parameter is an untyped object with additionalProperties=true, meaning the schema gives the agent no key names at all. The description does not list or hint at any updatable fields, so the caller has no way to construct a valid payload without guessing.

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 (Update) and resource (service principal), which is enough to separate it from create_service_principal, delete_service_principal, and get_service_principal_by_id in the sibling list. It stops short of naming which parts of a service principal are updatable.

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 indication of when to use this versus create_service_principal or delete_service_principal, and no prerequisites such as required permissions or the need for an existing sp_id. The agent is left to infer usage entirely from the name.

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