Wicked MCP server

paywall_import_routes

Bulk upsert multiple API routes with their prices, networks and payout wallets in one call to paywall a whole API at once, keyed on method and path.

Instructions

[x402 Paywall] Bulk upsert routes keyed on (method, path) — paywall a whole API in one call (needs PAYWALL_API_KEY).

Use when you want to paywall many routes in one call (upsert on method and path). Not for a single route (use paywall_create_route).

Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

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": {
      "routes": "<routes>"
    },
    "name": "paywall_import_routes"
  }
}

Input Schema

Name	Required	Description	Default
`routes`	Yes	Route objects, same fields as paywall_create_route.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Goes beyond the annotations by naming the required credential (PAYWALL_API_KEY) and stating that state is written upstream, which an agent needs before calling. One caveat: 'upsert keyed on (method, path)' implies repeat-safe behavior while the annotations declare idempotentHint=false — this is a mild tension worth noting, though not a flat contradiction since upserts can still mutate existing fields.

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?

Purpose is front-loaded and the three sentences are short. There is minor redundancy ('upsert on method and path' restated in the usage sentence) and the trailing 'needs the credentials or wallet signature noted above where applicable' is boilerplate that could be trimmed to the concrete key requirement.

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?

Covers what it does, when to use it, and the auth requirement, which is adequate for a one-parameter tool with annotations and no output schema. It is silent on bulk-specific behavior an agent would want: partial-failure semantics (atomic vs per-route), maximum batch size, and what the call returns on success.

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 the route item fields (price, network, payTo, upstreamUrl, asset) are already fully documented in the schema, so the description adds little per-field meaning. Its only extra value is the cross-reference that route objects use 'same fields as paywall_create_route'.

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 and resource ('Bulk upsert routes') plus the key ('method, path') and the outcome ('paywall a whole API in one call'). It explicitly names the sibling it is not (paywall_create_route), so the agent can distinguish bulk from single-route operations without opening a schema.

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

Usage Guidelines5/5

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

'Use when you want to paywall many routes in one call' gives the positive condition, and 'Not for a single route (use paywall_create_route)' names the exclusion and the alternative. This is the explicit when/when-not/alternative pattern.

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

Deploy Server