ALPNAI — Agent Performance Tools

Change Set purchase

purchase_changes

DestructiveIdempotent

Get Change Set for 0.05 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?

Goes well beyond the annotations by describing the cost, test budget debit, PaymentRequired response, retry mechanics with signed PaymentPayload, settlement metadata, and REST header support. The security note about never sending a private key adds important operational context. No contradiction with 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?

Information-dense and front-loaded with the core purchase action, followed by modes, retry flow, alternatives, and security. Every sentence contributes, though the dense paragraph format could be slightly easier to scan.

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?

Covers the payment flow, retries, response fields, pending-order behavior, headers, and safety guidance, which is strong for a payment tool without an output schema. The main gap is the unexplained 'since' parameter.

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?

The description adds meaning for idempotency_key (retry with same key) and mode (sandbox/live conditions), which the schema only partially covers. However, the 'since' parameter remains undocumented by both schema and description, so it does not fully compensate for the 50% schema coverage.

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?

States a specific verb and resource ('Get Change Set') plus the cost ('0.05 USDC'), making the tool's function immediately clear. It also distinguishes itself from the free sample flow and from get_order for pending orders.

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?

Explicitly explains when to use sandbox vs live mode, when to retry with the same idempotency key, and when to call get_order instead of submitting another payment. It gives clear when/when-not guidance and names an alternative tool.

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?