scdo-agent-plugins

Overview Schema Source Related Servers Discussions Admin

Book income

book_income

Record a settled x402 payment as agent income on the Agent Ledger by verifying its signature, payee wallet, and on-chain receipt; duplicate bookings are safely ignored.

Instructions

Book a settled x402 payment the agent received as income on the Agent Ledger. The ledger checks the signature, the payee wallet and the on-chain receipt. Booking twice is safe (duplicate). agent: 0x agent address if not a local bot.

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": {
      "paymentPayload": "<paymentPayload>",
      "settlement": "<settlement>"
    },
    "name": "book_income"
  }
}

Input Schema

Name	Required	Description	Default
`bot`	No
`agent`	No
`settlement`	Yes
`paymentPayload`	Yes
`paymentRequirements`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the ledger validates signature, payee wallet and on-chain receipt, and booking is idempotent. However, it omits auth/permission requirements, failure behavior, and what a successful booking returns.

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

Conciseness3/5

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

The purpose is front-loaded and the text is short, but the trailing fragment 'agent: 0x agent address if not a local bot.' reads as a dangling note rather than an integrated sentence. It is efficient without being well structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations, no output schema and 0% parameter documentation, the description should do much more. It covers validation and idempotency but leaves the required payload/settlement semantics and the other optional parameters unexplained.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, so the description must compensate and largely does not. It adds meaning only for 'agent' (a 0x address when not a local bot), leaving bot, settlement, paymentPayload and paymentRequirements undocumented in both the schema and the description.

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 (book) and resource (a settled x402 payment received as income on the Agent Ledger), which cleanly separates it from the outbound sibling pay_x402. It is clear what the tool does, though it does not name siblings explicitly for differentiation.

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?

The phrase 'a settled x402 payment the agent received as income' implies the tool is used after settlement, and 'Booking twice is safe' hints at retry behavior, but no explicit when-to-use/when-not or named alternative is given. Guidance is only implied.

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