AgentWallet MCP Server

get_paywall

Retrieve details for a specific x402 paywall by ID, including pricing, access URL, payment stats, and configuration. Use it to inspect a paywall’s setup before payments or access decisions.

Instructions

Get details for a specific x402 paywall by ID. Returns pricing, access URL, payment stats, and configuration.

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": {
      "paywall_id": "<paywall_id>"
    },
    "name": "get_paywall"
  }
}

Input Schema

Name	Required	Description	Default
`paywall_id`	Yes	Paywall ID

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.14.8Oct 27, 2026
- addedInput schema / properties / paywall_id / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / paywall_id / minimum
```
Added value: +-9007199254740991
```
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?

With no annotations, the description must carry the behavioral burden. It discloses the response content and implies a passive read via 'Get', but says nothing about behavior for an unknown/nonexistent ID, authentication or ownership requirements, or whether stats are live or cached.

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 with zero filler; the identity of the resource is front-loaded and the return-value summary follows immediately. Nothing extraneous.

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 one-parameter read tool with no annotations and no output schema, the description covers purpose, input source, and roughly what is returned. Only error/permission behavior is left unstated, which is a minor gap at this complexity.

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 coverage is 100% and the single parameter is already documented as 'Paywall ID'. The description's 'by ID' adds no format, source, or validation 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 ('Get details for a specific x402 paywall') and scopes it with 'by ID', plus enumerates what comes back (pricing, access URL, payment stats, configuration). It is clearly a single-resource read, distinct from list_paywalls and get_paywall_payments in shape, though no sibling is named explicitly.

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?

Usage is only implied: 'by ID' suggests a lookup once an ID is known, but there is no guidance on when to prefer this over list_paywalls (e.g., to discover IDs) or get_paywall_payments (for payment history). No prerequisites or exclusions are stated.

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