Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get Application By Id

get_application_by_id
Read-only

Get a specific application by its object ID.

Instructions

Get a specific application 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": {
      "app_id": "<app_id>"
    },
    "name": "get_application_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

readOnlyHint=true already covers the safety profile, and the description adds nothing on top of it — no statement about behavior when the ID does not exist, and no indication of what 'object ID' means in this API's terms. It restates the operation rather than disclosing traits.

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?

One short sentence with zero waste and the lookup key front-loaded. Appropriately sized for a trivial single-parameter read, though it leaves room without being padded.

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?

An output schema exists and annotations cover safety, so the remaining burden is small, but for a lookup tool the description says nothing about not-found behavior or where the object ID comes from (e.g., list_applications), leaving a modest gap.

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%, so the description carries the burden for the single parameter; it does clarify that app_id is an 'object ID' (not a display name or client ID), which is real added meaning, but it gives no format or sourcing guidance.

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 application') plus the lookup key ('by its object ID'), which cleanly separates it from list_applications and the create/update/delete siblings. It never names an alternative explicitly, so it stops short of a 5.

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?

Usage is only implied: 'by its object ID' signals this is the tool for when you already hold an ID rather than searching, but there is no explicit when-to-use, prerequisite, or reference to list_applications for discovery.

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