Skip to main content
Glama
Sign In
PingOne Advanced Identity Cloud MCP Server

PingOne Advanced Identity Cloud MCP Server

Official
by pingidentity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List OIDC Apps

listOidcApps
Read-only

Retrieve a list of OIDC applications with summary fields for a specified realm. Filter by query to narrow results.

Instructions

Lists OIDC applications in a realm with summary fields only. Use getOidcApp for full details of a specific app.

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": {
      "realm": "<realm>"
    },
    "name": "listOidcApps"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesThe realm
queryFilterNoOptional CREST query filter. Default: true (all apps). Example: name sw "my"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate readOnly and openWorld. The description adds that only summary fields are returned, which is useful behavioral context. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no extraneous information. Purpose is front-loaded, and the alternative guidance is concise.

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?

For a simple list tool with only two parameters, the description is adequate. It clarifies the output scope but could explicitly mention return type (array of objects). Minor gap, but overall complete given low complexity.

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?

Input schema has 100% coverage with descriptions for both parameters. The description adds no additional meaning beyond what schema provides, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists OIDC applications in a realm and specifies that only summary fields are returned. It distinguishes from sibling getOidcApp by mentioning full details are available there.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly guides to use getOidcApp for full details, providing clear when-to-use vs alternative. No mention of when not to use, but the context is sufficient.

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

Deploy Server

Other Tools