XPayr MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

xpayr_get_public_payment_status

Retrieve real-time public checkout status for a payment session, including on-chain transaction hash, sender wallet, block confirmations, and paid timestamp without an API key.

Instructions

Poll real-time public checkout status, on-chain tx_hash, sender wallet address, block confirmations, and paid_at timestamp for any session (public endpoint, no API key required).

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": {
      "session_id": "<session_id>"
    },
    "name": "xpayr_get_public_payment_status"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	Payment session ID (e.g., ps_6b5b7d8737c0e0ec0a04a29a045d2d5d).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations supplied, the description does real work: it discloses that this is an unauthenticated public endpoint requiring no API key, that it is intended for polling (so repeated calls are expected), and which state fields are returned. It stops short of covering failure behavior (unknown/expired session), rate limits, or freshness guarantees.

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?

One sentence, verb first, return fields in the middle, and the access-mode caveat in a parenthetical at the end. Nothing is redundant and the key routing signal (no API key needed) is not buried.

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?

For a one-parameter read tool with no output schema, the description compensates well by naming the returned fields and the auth model. The main remaining gap is behavior on non-existent or unpaid sessions, which an agent polling this endpoint would want to know.

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 single session_id parameter includes a format example, so the schema carries the parameter documentation. The description adds only the qualifier "for any session", which mildly widens scope beyond merchant ownership, so 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?

The description uses a specific verb ("Poll") and resource ("public checkout status") and enumerates exactly which fields come back (tx_hash, sender wallet address, confirmations, paid_at). It also signals the differentiating trait versus xpayr_get_payment_session ("public endpoint, no API key required"), though it never names that sibling explicitly.

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

Usage Guidelines3/5

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

"Poll" implies a repeated-call usage pattern and "for any session" signals broad applicability, but there is no explicit when-to-use/when-not guidance and no reference to xpayr_get_payment_session or xpayr_list_payment_sessions as alternatives. The agent must infer the selection rule from the word "public" alone.

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