Skip to main content
Glama
pingidentity

PingOne Advanced Identity Cloud MCP Server

Official
by pingidentity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Managed Object Schema

getManagedObjectSchema
Read-only

Retrieves the schema definition for a specified managed object type in PingOne Advanced Identity Cloud, optionally including full configuration details.

Instructions

Retrieve schema definition for a managed object type in PingOne AIC

Input Schema

NameRequiredDescriptionDefault
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.
includeFullDefinitionNoWhen true, returns the complete managed object definition including script hooks, lifecycle metadata, notifications, and other configuration. Defaults to false for a concise schema-only response.

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 / includeFullDefinition
      Added value: +{
+  "default": false,
+  "description": "When true, returns the complete managed object definition including script hooks, lifecycle metadata, notifications, and other configuration. Defaults to false for a concise schema-only response.",
+  "type": "boolean"
+}
  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 readOnlyHint=true and openWorldHint=true, so the safety profile is already covered. The description adds the environment ('PingOne AIC') but no additional behavioral details such as rate limits, error conditions, or what the returned schema contains. With annotations present, a 3 is appropriate.

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 wasted words. It immediately states the action 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?

For a simple two-parameter retrieval tool with no output schema, the description states what is returned ('schema definition') but not the return format or structure. Given the rich annotations and complete parameter schema, this is minimally adequate but leaves an agent guessing about the output shape.

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 both parameters are fully documented in the input schema. The description adds no parameter-level detail beyond what the schema provides, which is the baseline expectation.

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 ('Retrieve') and resource ('schema definition for a managed object type'), which distinguishes it from getManagedObject (which returns an instance). However, it does not explicitly contrast with other schema tools like getThemeSchema or getOidcAppSchema, so no sibling differentiation beyond the resource name.

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?

No when-to-use or when-not-to-use guidance. The schema's objectType description mentions using listManagedObjects to discover types, but that is in the schema, not the tool description. No alternatives are named, so an agent must infer usage from the name alone.

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