XPayr MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

xpayr_list_agent_payment_intents

List AI agent payment intents with policy evaluation decisions and audit trail records for your merchant account. Filter results by decision status or limit the number of records returned.

Instructions

List AI agent payment intents, policy evaluation decisions, and audit trail records for the merchant.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "xpayr_list_agent_payment_intents"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum records to return.
`status`	No	Filter by decision status (approved, pending_approval, rejected, bridged).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden. 'List' implies read-only, but nothing is said about ordering, pagination behavior, whether audit trail entries are embedded per intent or listed flat, retention window, or whether results include intents across all agents or only the calling merchant's agents.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler, but its compactness comes at the cost of clarity about the three-way record composition.

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-optional-parameter read tool with a fully documented schema and no output schema, the description is minimally adequate. It still leaves the shape of returned records and the relationship between intents, policy decisions, and audit entries unexplained, which matters for an agent that must parse the result.

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%, with 'limit' and 'status' fully documented including the accepted status values, so the baseline is 3. The description adds nothing about defaults, max limit values, or how status filtering interacts with audit trail records.

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 ('List') and concrete resources ('AI agent payment intents, policy evaluation decisions, and audit trail records'), scoped to the merchant. It does not, however, distinguish itself from the sibling xpayr_list_payment_sessions or clarify whether the three record types are returned together in one feed or are separate list modes.

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?

There is no guidance on when to use this tool versus xpayr_list_payment_sessions, xpayr_get_payment_session, or the intent-action siblings (approve/reject/bridge). An agent must infer from the name alone that this is the read path for intents.

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