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

Query Managed Objects

queryManagedObjects
Read-only

Query managed objects in PingOne Advanced Identity Cloud with CREST filter syntax to retrieve, filter, sort, and paginate user, role, group, or organization data.

Instructions

Query managed objects in PingOne AIC using CREST query filter syntax

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated field names to return. If omitted, returns all fields. Example: "FIELD1,FIELD2,_id"
pageSizeNoNumber of objects to return per page (default: 50)
sortKeysNoComma-separated field names to sort by. Prefix with "-" for descending. Example: "FIELD1,-FIELD2"
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.
queryFilterNoCREST query filter expression. IMPORTANT: Call getManagedObjectSchema first to discover available fields. Operators: eq, co, sw, gt, ge, lt, le, pr (present), ! (NOT). Boolean: and, or. Quote strings. If omitted, returns all objects up to pageSize. Examples: FIELD eq "value" | FIELD sw "prefix" | (FIELD1 eq "a") and (FIELD2 co "b") | FIELD pr Docs: https://docs.pingidentity.com/pingoneaic/latest/developer-docs/crest/query.html#crest-query-queryFilter
pagedResultsCookieNoPagination cookie from previous response to retrieve next page

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. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the filter-syntax mention and discloses nothing about pagination semantics (pageSize default, pagedResultsCookie flow), result caps, or any authorization requirements.

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 filler; the key concept (CREST query filter syntax) appears immediately. Nothing to trim.

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?

With no output schema, the description should say something about what is returned (object shape, paging behavior), and it does not. The rich schema partially compensates, but for a 6-parameter query tool the description is thinner than ideal.

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% and the queryFilter property documents operators, boolean combinators, quoting, examples, and a docs link. The description adds no parameter meaning beyond what the schema already says, so the baseline 3 applies.

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 (Query) and resource (managed objects) plus the filter dialect (CREST query filter syntax), so the agent knows it is a filtered read. However, it does nothing to distinguish it from the very similarly named siblings listManagedObjects and getManagedObject, leaving that differentiation to the schema.

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?

The description gives no when-to-use guidance and never names an alternative. The routing hints (use listManagedObjects to discover types, call getManagedObjectSchema first) appear only inside the schema's parameter descriptions, not in the description itself, so the description provides no usage guidance of its own.

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