AgentWallet MCP Server

update_paywall

Modify an x402 paywall configuration—such as price, resource URL, active status, or other fields—by paywall ID. Use it to adjust access controls for AI agent payments.

Instructions

Update an x402 paywall configuration. Can change price, resource URL, active status, or any other field.

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

Input Schema

Name	Required	Description
`name`	No	New paywall name
`amount`	No	New price in human-readable format (e.g. "0.05")
`is_active`	No	Enable (true) or disable (false) the paywall
`paywall_id`	Yes	Paywall ID to update
`description`	No	New description
`resource_url`	No	New resource URL
`resource_mime`	No	New MIME type
`token_decimals`	No	Token decimals. Read from the paywall itself when omitted

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
```
Changed3 schema fields changedv1.14.2Oct 14, 2026
- changedInput schema / properties / token_decimals / description
```
Previous value: -"Token decimals (needed if changing amount)"New value: +"Token decimals. Read from the paywall itself when omitted"
```
- addedInput schema / properties / token_decimals / maximum
```
Added value: +36
```
- addedInput schema / properties / token_decimals / minimum
```
Added value: +0
```
First observedv1.7.3Mar 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. It never states whether omitted fields are preserved or reset, whether the caller needs ownership/permission, whether changes are reversible, or what happens to live payment flows — all critical for a mutation with 8 fields and only 1 required.

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?

Two short sentences, front-loaded with the resource being modified. The closing 'or any other field' is vague filler that earns little, keeping it from a 5.

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?

A mutation tool with no annotations, no output schema and ambiguous partial-update semantics needs the description to explain what an update does to existing state. Nothing about replace-vs-merge behavior, validation failures, or permissions is covered.

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%, so baseline is 3. The description names price, resource URL and active status, matching schema fields, but adds no semantics (e.g. partial-update behavior, amount formatting vs token_decimals) beyond what the schema already documents.

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 (update) and resource (x402 paywall configuration) plus the dimensions that can change. It is clearly a mutating counterpart to create_paywall/get_paywall/delete_paywall, though it does not name those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says what can be changed but never when to use this tool rather than create_paywall, delete_paywall, or list_paywalls, and gives no prerequisites or exclusions. The only inference an agent can draw is 'the paywall already exists'.

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