Find newly added L402 and x402 paywalled APIs in the directory. Filter by protocol and limit to discover new services as they launch.
Get the most recently added L402/x402 services in the directory — useful for discovering new paywalled APIs as they launch.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 10) | |
| protocol | No | Filter by protocol (optional) |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the ordering behavior ('most recently added') but does not describe the result shape, pagination behavior, any auth constraints, or whether the protocol filter applies exact or union matching. This is a meaningful gap for a tool with no annotation hints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that names the action, resource, and use case without redundancy. Every word earns its place, and there is no filler or restatement of the tool name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity, read-only lookup with two optional parameters and 100% schema coverage, the description plus schema provides enough context for an agent to select and call the tool. It lacks an explicit return-value description because no output schema exists, but that is not critical for invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents both parameters thoroughly: 'limit' has a default and meaning, and 'protocol' has an explicit enum. The description adds no additional parameter-level semantics, so the high schema coverage justifies the baseline score.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the operation ('Get'), the resource ('L402/x402 services in the directory'), and the distinguishing scope ('most recently added'). It also adds the use-case nuance of discovering new paywalled APIs, which separates it from sibling tools like search, category listing, and single-service lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'useful for discovering new paywalled APIs as they launch' provides clear context for when to use this tool. It does not explicitly name alternatives or exclusion conditions, but the intended use case is evident enough for an agent to select it over category/search/list tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.