Get Paywall Status
get_paywall_statusFREE. Show whether inbound x402 paywall is enabled, inbound price, network, and Merchant payTo address.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
402 Dispatcher
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of explaining behavior. It adds the useful 'FREE' cost signal and describes a read-only 'show' operation, but it does not explicitly state that the tool has no side effects or describe the response format or error cases.
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?
The description is a single, tightly scoped sentence with no filler. The 'FREE' marker is front-loaded and the data fields are listed efficiently.
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 zero-parameter status-checking tool with no output schema, the description names the key pieces of returned information and identifies the domain. It could be slightly richer by stating value types (e.g., boolean for enabled, currency for price), but it is substantially complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema is empty, so there is nothing for the description to add about inputs. The described return fields (enabled, price, network, payTo) help set expectations for what the no-argument call will reveal.
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 ('Show') and a precise resource ('inbound x402 paywall status'), then enumerates the returned fields: enabled, price, network, and Merchant payTo address. This clearly distinguishes it from the many sibling weather, chain, and API-calling tools.
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 intended use is implied: call this to inspect whether the inbound x402 paywall is enabled and what its configuration is. However, the description does not explicitly state when to prefer this tool over alternatives like call_x402_api or quote_route.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.6/5.0
Disambiguation1/5
The core dispatcher tools are distinct, but the 84 auto-discovered wrappers contain dozens of near-identical news, weather, and translation endpoints. An agent cannot reliably tell many of these apart without reading provider-specific details, and misselection is likely.
Naming Consistency2/5
Core tools use a readable verb_noun pattern, but most tools are machine-generated `x402_<domain>_<path>_<number>` names with opaque numeric suffixes. The two naming schemes are mixed, and the generated names are not intuitive.
Tool Count1/5
95 tools is an extreme mismatch for a coherent MCP surface. The bulk are auto-registered third-party proxies that duplicate the same few categories, creating massive prompt bloat and selection overhead.
Completeness4/5
For an x402 dispatcher, the core lifecycle is well covered: discovery, search, quote, route-and-call, stats, paywall status, and cashflow/P&L. Minor gaps such as no deregistration or detailed per-transaction drill-down exist, but main workflows do not dead-end.