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

Patch Managed Object

patchManagedObject

Update specific fields of a PingOne AIC managed object using JSON Patch operations, applying add, remove, or replace changes to keep identity data accurate without full overwrites.

Instructions

Update specific fields of a managed object in PingOne AIC using JSON Patch operations

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": {
      "objectType": "<objectType>",
      "objectId": "<objectId>",
      "revision": "<revision>",
      "operations": "<operations>"
    },
    "name": "patchManagedObject"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectIdYesThe object's unique identifier (_id)
revisionYesThe current revision (_rev) of the object, obtained from getManagedObject
objectTypeYesManaged object type (e.g., alpha_user, bravo_user, alpha_role, bravo_role, alpha_group, bravo_group, alpha_organization, bravo_organization). Use listManagedObjects to discover all available types.
operationsYesArray of JSON Patch operations to apply to the object

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • removedInput schema / properties / objectType / minLength
      Removed value: -1
    • addedInput schema / properties / objectType / pattern
      Added value: +"^[a-zA-Z0-9_]+$"
  2. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / revision / minLength
      Added value: +1
  3. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare openWorldHint=true and destructiveHint=false, lowering the burden. The description adds that changes are partial field updates via JSON Patch, but omits important behavioral context such as revision-based optimistic concurrency, atomicity of operations, or error behavior.

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?

A single front-loaded sentence with no redundant clauses; every word contributes to identifying the action and mechanism.

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?

The schema covers all parameters and annotations cover safety hints, but the description does not explain revision-based concurrency or the implications of JSON Patch operations like remove. For a mutation tool with no output schema, it is minimally adequate.

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 description coverage is 100%, so all four required parameters are already documented. The description adds no parameter-level meaning beyond identifying the operation as JSON Patch.

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), resource (managed object), mechanism (JSON Patch operations), and product (PingOne AIC). It does not explicitly differentiate from sibling tools like patchManagedObjectDefinition or patchManagedObjectRelationship, 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 Guidelines2/5

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

Provides no guidance on when to use this tool versus alternatives such as patchManagedObjectDefinition, updateTheme, or other update siblings. The schema mentions getManagedObject for revision, but the description itself gives no usage context or exclusions.

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