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

Update OIDC App

updateOidcApp
Idempotent

Update an OIDC application by modifying its client configuration or applying JSON Patch operations to metadata. Specify realm and application name to apply changes.

Instructions

Updates an OIDC application. You can update the client configuration, the application metadata, or both.

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": "<name>"
    },
    "name": "updateOidcApp"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe application name
realmYesThe realm
oauth2ClientNoPartial OIDC client configuration. Provide only the properties you want to change, nested under their configuration sections. Omit to skip this update.
managedApplicationNoApplication metadata patch. Omit to skip this update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

The description discloses that the tool modifies an OIDC application, which is consistent with annotations (idempotentHint, openWorldHint). However, it does not elaborate on specific behaviors like the need for a current revision or potential side effects beyond the update scope.

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?

The description is extremely concise, using two sentences to convey the core purpose and options. No extraneous information, front-loaded with the verb and resource.

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?

Given the tool's complexity (nested objects, no output schema), the description covers the main update types but lacks context on prerequisites (e.g., fetching _rev via getOidcApp) and return behavior. The openWorldHint suggests possible unlisted effects, but the description could still be more complete.

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?

With 100% schema coverage, the description adds minimal parameter semantics beyond the schema, only summarizing that client config and metadata can be updated. It does not detail the structure or required fields like _rev for metadata.

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 updates an OIDC application, specifying that it can update client configuration, application metadata, or both. This clearly distinguishes it from sibling tools like createOidcApp or deleteOidcApp.

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?

The description indicates when to use the tool (to update an existing OIDC app) but does not explicitly mention when not to use it, such as if the app doesn't exist (use create) or prerequisites like obtaining the current revision from getOidcApp for metadata updates.

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