Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Update Application

update_application
Destructive

Update an existing application (app registration).

Instructions

Update an existing application (app registration).

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": {
      "app_id": "<app_id>",
      "app_data": "<app_data>"
    },
    "name": "update_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYes
app_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 readOnlyHint=false and destructiveHint=true, so the safety profile is carried structurally, but the description adds nothing about what is destructively changed — e.g., whether app_data replaces or merges into existing registration fields, or whether credentials/secrets are affected. For a destructive mutation this leaves a real gap.

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?

A single front-loaded sentence with zero waste, but it is under-specified rather than economical — it omits information an agent needs rather than trimming unused detail.

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?

Output schema exists, so return values need not be explained, but for a destructive update with two undocumented parameters (including a free-form object) and no behavioral notes, the definition is not complete enough to call safely.

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 description never mentions app_id or the open-ended app_data object. The nested app_data (additionalProperties: true) is entirely undefined, leaving the merge/replace semantics and acceptable keys completely unknown — the description does not compensate for the coverage gap at all.

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 (existing application/app registration), which is clear enough to distinguish it from list/get/create/delete_application siblings by intent. However, it offers no explicit differentiation from update_service_principal or update_group, and 'app registration' parenthetical is the only disambiguation hint.

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 guidance on when to use this versus update_service_principal or create_application. Only 'existing' implies a pre-existing app must be identified, with no stated prerequisites, permissions, or exclusions.

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