Skip to main content
Glama
pingidentity

PingOne Advanced Identity Cloud MCP Server

Official
by pingidentity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Query Environment Secrets and Variables (ESVs)

queryESVs
Read-only

Retrieve environment secrets and variables from PingOne AIC by ID, with pagination and sorting.

Instructions

Query environment secrets or variables (ESVs) in PingOne AIC by ID

Input Schema

NameRequiredDescriptionDefault
typeYesType of ESV to query
pageSizeNoNumber of results to return per page (default: 50)
sortKeysNoComma-separated field names to sort by. Prefix with "-" for descending. Example: "_id,-lastChangeDate"
queryTermNoSearch term to filter by ID. If omitted, returns all ESVs up to pageSize
pagedResultsCookieNoPagination cookie from previous response to retrieve next page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already mark readOnlyHint and openWorldHint. The description adds no behavioral details beyond the schema, such as pagination behavior or response format.

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?

Single sentence of 12 words, perfectly concise and front-loaded with the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters, no output schema, no guidance, and minimal description, the tool is underdescribed. The description only states the purpose, missing details on pagination, sorting, and response.

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 has 100% coverage with descriptions for all parameters. The description does not add any additional meaning beyond what the schema provides.

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 verb 'Query', the resource 'ESVs', and the context 'in PingOne AIC'. It distinguishes from sibling tools like getVariable and deleteVariable by being a query operation for ESVs.

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 guidance on when to use this tool versus alternatives like getVariable for a single retrieval. The description does not specify use cases 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