agentpay — card-funded wallets for AI agents

Get proof-of-spend attestation

get_attestation

Ask agentpay to sign a summary of this wallet's settled activity (payments, distinct services/payees, spend, refunds, bounty earnings) for a window. Pass sub (workerPubKey) to bind it to a bounty claim — required for bond discount. Free.

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": "get_attestation"
  }
}

Input Schema

Name	Required	Description
`key`	No	Agent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.
`sub`	No	Claimant binding, e.g. workerPubKey for a bounty claim
`days`	No	Window in days (default 30)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 11, 2026

addedInput schema / properties / sub

Added value: +{
+  "description": "Claimant binding, e.g. workerPubKey for a bounty claim",
+  "maxLength": 120,
+  "type": "string"
+}

AddedSep 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries full behavioral burden. It usefully discloses that the result is agentpay-signed, enumerates the summarized activity, notes it is 'Free', and that sub binding affects bond discount. It omits auth requirements (key/Bearer interplay), whether the signature is revocable, and what the signed output actually is.

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?

Two tight sentences, front-loaded with the core action and scope, followed by the parameter caveat and cost. No filler; every clause earns its place.

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?

With no output schema and no annotations, the description should explain the return shape, but it never says what a signed attestation looks like or how auth is handled. It covers what is summarized well but leaves the output and auth story incomplete for a signing tool.

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 100%, so baseline is 3, but the description adds meaning beyond the schema by tying sub to a business consequence ('required for bond discount') and framing days as a 'window'. key and days remain schema-only, so it does not fully elaborate every parameter.

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 ('sign a summary') and resource (this wallet's settled activity), and enumerates the included dimensions (payments, services/payees, spend, refunds, bounty earnings), which no sibling like get_receipt or list_transactions does. An agent can tell this is a signed aggregate attestation, distinct from a raw receipt or transaction list.

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?

It gives one conditional rule — pass sub to bind to a bounty claim, required for bond discount — which is useful usage context. However, it never states when to prefer this over get_receipt or list_transactions, nor any exclusions, so the guidance is only partial and implied.

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

All agentpay — card-funded wallets for AI agents 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?