AgentWallet MCP Server

list_paywalls

Lists all x402 paywalls with IDs, names, pricing, access URLs, payment counts, and revenue totals to help agents review payment endpoints and performance.

Instructions

List all your x402 paywalls. Returns paywall IDs, names, pricing, access URLs, payment counts, and revenue totals.

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

Input Schema

Name	Required	Description	Default
`page`	No	Page number
`per_page`	No	Results per page (max 100)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.14.8Oct 27, 2026
- addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / page / minimum
```
Added value: +-9007199254740991
```
Changed2 schema fields changedv1.14.2Oct 14, 2026
- addedInput schema / properties / per_page / maximum
```
Added value: +100
```
- addedInput schema / properties / per_page / minimum
```
Added value: +1
```
First observedv1.7.3Mar 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the return fields (IDs, names, pricing, URLs, payment counts, revenue) in the absence of an output schema, but says nothing about ordering, pagination behavior, empty results, or auth requirements.

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 short sentences, purpose first, return shape second, with no filler. Every clause carries information an agent can use.

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 simple zero-required-parameter list tool, disclosing the returned fields compensates well for the missing output schema. The main gap is that result ordering and page-walking behavior are not described.

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 both pagination parameters (page, per_page with max 100) are fully documented there. The description adds no paging detail beyond the schema, so the 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?

States a specific verb and resource ('List all your x402 paywalls') and the returned fields make the scope concrete. It implicitly contrasts with the singular get_paywall, but never names it, so the differentiation is left to inference.

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 word 'List all' implies a browsing use case, but there is no explicit when-to-use versus get_paywall or list_payments, and no stated exclusions or prerequisites. Usage is inferable but not guided.

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