Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

List Applications

list_applications
Read-only

List all applications (app registrations) in the tenant, with paging.

Instructions

List all applications (app registrations) in the tenant, with paging.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's added burden is low. It contributes one behavioral fact ('with paging'), however it never explains how paging actually works — there is no page/cursor/skip parameter in the schema, so an agent cannot tell whether it must loop, vary limit, or follow a token from the output. That's a meaningful disclosure 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 tight sentence with the resource and scope front-loaded; nothing is wasted. The trailing 'with paging' is the one clause that promises more than it delivers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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-shape explanation is not required, and readOnlyHint covers the safety profile. The only substantive hole is pagination mechanics — with just a 'limit' parameter and no cursor, the description should clarify how to retrieve subsequent pages, which it does not.

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

Parameters2/5

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

Schema description coverage is 0% for the single parameter 'limit' (integer, default 100), and the description adds nothing about it — no maximum, no interaction with paging, no note that it caps results per page. The word 'paging' gestures at the parameter without explaining it, so the description does not compensate for the coverage gap.

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?

Specific verb+resource ('List all applications') with a clarifying gloss '(app registrations)' that disambiguates from service principals, a real sibling concern. It doesn't explicitly contrast with get_application_by_id, but 'list all' versus 'get ... by_id' makes the distinction inferable from the names.

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?

'List all ... in the tenant' implies the bulk-enumeration use case and implicitly routes single-record lookups to get_application_by_id, but no alternative is named and no when-not guidance (e.g., use search/filter tools for large tenants) is given.

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