ALPNAI — Agent Performance Tools

Evidence Pack purchase

purchase_evidence

DestructiveIdempotent

Get Evidence Pack for 0.25 USDC. Default mode sandbox creates a test receipt and debits only the test budget. Explicit mode live uses x402 only when commerce, owner mandate and billing eligibility are enabled. An unpaid result contains PaymentRequired in structuredContent and content. Retry the same tool and idempotency key with the signed PaymentPayload in params._meta["x402/payment"]. Confirmed settlement is returned in result._meta["x402/payment-response"]. For a pending order, call get_order with the original order_id; do not submit another payment. REST continuation and PAYMENT-SIGNATURE headers remain supported. Never send a private key.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Sandbox is the default. Live explicitly requests the existing authorized x402 purchase flow.	sandbox
`since`	No
`mandate_id`	No	Owner-authorized commercial mandate ID. Alternatively send X-AlpNAI-Mandate in the MCP request headers.
`idempotency_key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 15, 2026

addedInput schema / properties / mandate_id

Added value: +{
+  "description": "Owner-authorized commercial mandate ID. Alternatively send X-AlpNAI-Mandate in the MCP request headers.",
+  "pattern": "^[-a-zA-Z0-9]{8,80}$",
+  "type": "string"
+}

addedInput schema / properties / mode

Added value: +{
+  "default": "sandbox",
+  "description": "Sandbox is the default. Live explicitly requests the existing authorized x402 purchase flow.",
+  "enum": [
+    "sandbox",
+    "live"
+  ],
+  "type": "string"
+}

First observedSep 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes far beyond the annotations by explaining what each mode does, where PaymentRequired appears, how to retry with params._meta['x402/payment'], and where settlement appears in result._meta. It also warns 'Never send a private key.' Nothing contradicts the readOnlyHint=false, idempotentHint=true, or destructiveHint=true annotations.

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?

The description is dense but front-loaded with the core purpose, and every major behavioral point earns its place. A few trailing details like 'REST continuation and PAYMENT-SIGNATURE headers remain supported' add minor noise, but the overall structure is efficient for a payment-flow tool.

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?

Given no output schema, the description compensates well by describing PaymentRequired, retry flow, settlement response location, and pending-order fallback. The main gap is the undocumented 'since' parameter, which leaves a small ambiguity in an otherwise complete operational picture.

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

Parameters4/5

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

Schema description coverage is 50%, so the description must compensate. It adds real meaning for idempotency_key by tying it to PaymentPayload retries, and for mode by explaining sandbox versus live eligibility. However, the 'since' parameter remains completely unexplained in both schema and description, preventing a top score.

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 opens with a specific verb and resource: 'Get Evidence Pack for 0.25 USDC.' It also clarifies the sandbox versus live behavior, making the tool's purpose unmistakable and distinct from nearby retrieval tools like get_order and get_catalog.

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

Usage Guidelines5/5

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

It gives explicit when-to-use conditions, including 'Explicit mode live uses x402 only when commerce, owner mandate and billing eligibility are enabled,' and it names the alternative: 'For a pending order, call get_order with the original order_id; do not submit another payment.' This is strong, actionable routing guidance.

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

All ALPNAI — Agent Performance Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?