Skip to main content
Glama
pingidentity

PingOne Advanced Identity Cloud MCP Server

Official
by pingidentity
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Query Logs

queryLogs
Read-only

Query PingOne AIC logs to investigate issues, debug authentication failures, and trace specific requests using transaction IDs.

Instructions

Query PingOne AIC logs to investigate issues or understand system behavior. Useful for debugging journey execution failures, authentication errors, script exceptions, and API issues. Transaction IDs from error responses can be used to trace specific requests.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourcesYesLog sources to query (e.g., ['am-authentication', 'idm-activity']). IMPORTANT: use the getLogSources tool to determine available sources.
beginTimeNoStart time in ISO 8601 format without milliseconds (e.g., '2025-01-11T10:00:00Z'). Filters logs after this time. Defaults to 24 hours before endTime if omitted. Must be within 24 hours of endTime.
endTimeNoEnd time in ISO 8601 format without milliseconds (e.g., '2025-01-11T12:00:00Z'). Filters logs before this time. Defaults to current time if omitted. Must be within 24 hours of beginTime.
transactionIdNoTransaction ID to trace a specific request. Found in: (1) tool success/error messages, (2) x-forgerock-transactionid response header from AIC API calls, (3) browser network tab when debugging UI issues.
queryFilterNoCRITICAL: All field paths MUST start with / (e.g., /payload/level, /payload/principal). Missing the leading slash causes 500 Internal Server Error. Operators: eq, co, sw, lt, le, gt, ge, pr (present), ! (NOT). Boolean: and, or. Quote string values. Time filtering: Use beginTime/endTime parameters for time ranges. Use /payload/timestamp only for exact timestamp matches. Examples: /payload/level eq "ERROR" /payload/principal co "admin" /payload/eventName eq "AM-LOGIN-COMPLETED" (/payload/level eq "ERROR") and (/payload/http/request/path co "openidm") /payload/response.statusCode ge 400 Troubleshooting: If you receive a 500 error, verify all field paths begin with /
pagedResultsCookieNoOpaque pagination cookie from a previous response. Use this to retrieve the next page of results.
pageSizeNoMaximum logs to return (default 100).

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true. The description confirms its read-only nature ('Query... to investigate') and adds detail about transaction ID tracing. Parameter descriptions further disclose behaviors like leading slash requirement for queryFilter (causing 500 if missing). No contradictions.

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 three sentences front-loaded with purpose, use cases, and a key feature (transaction ID tracing). Every sentence adds value, and parameter descriptions are detailed but not verbose. No wasted words.

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

Completeness4/5

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

The description and parameter docs cover the tool's functionality well, including time constraints, pagination, and query filter usage. However, without an output schema, the return format (e.g., structure of log entries) is not described, leaving a minor gap for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds rich context, especially for transactionId (how to obtain it) and queryFilter (operators, examples, troubleshooting). This goes well beyond the schema definitions, providing actionable guidance.

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 queries PingOne AIC logs for debugging issues. It specifies the resource ('PingOne AIC logs') and verb ('Query'), and distinguishes from siblings like getLogSources by focusing on log investigation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives concrete use cases (debugging journey failures, authentication errors, etc.), providing clear guidance on when to use. It lacks explicit exclusions or alternative tool mentions, but the use cases are sufficiently specific.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pingidentity/aic-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server