Skip to main content
Glama
Sign In

Wicked MCP

by io.github.WickedAPI
OverviewDiscussionsAdmin

paywall_signup

[x402 Paywall] Create a tenant account. Returns a Bearer apiKey ONCE — store it and set PAYWALL_API_KEY. Rate-limited to 5/hour per IP.

Use when you want a paywall tenant account and its API key (shown once). Not for managing routes of an existing tenant.

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": {
      "name": "<name>",
      "slug": "<slug>"
    },
    "name": "paywall_signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesLetters, digits, space . _ - (max 100).
slugYesLowercase a-z0-9 and hyphens, 2-40 chars; becomes your mount path prefix /{slug}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description adds useful behavior beyond annotations: the API key is returned only once, must be stored, and signup is rate-limited to 5/hour per IP. It also confirms upstream state mutation, though the phrase "credentials or wallet signature noted above where applicable" is vague and points to nothing visible in the provided definition.

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?

The description is front-loaded and reasonably short, with creation, return value, and rate limit stated early. It repeats the one-time API key note and restates the read-only annotation, which slightly dilutes conciseness.

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

Completeness5/5

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

For a simple two-parameter signup tool with full schema coverage and annotations covering safety profile, the description supplies the critical missing context: one-time key return and rate limiting. No output schema exists, but the important return behavior is 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 parameters already have detailed constraints and usage notes in the schema. The description does not add meaningful semantics for `name` or `slug` beyond what the schema provides.

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?

The description uses a specific verb and resource: "Create a tenant account" for the x402 Paywall. It distinguishes this from route-management siblings with the explicit exclusion "Not for managing routes of an existing tenant."

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?

It states exactly when to use the tool: "Use when you want a paywall tenant account and its API key." It also states when not to use it by naming route management of an existing tenant as out of scope.

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

All Wicked MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources