Skip to main content
Glama
Sign In

Tlacuilo

by io.github.mastercobeos
OverviewDiscussionsAdmin

x402_find

x402_find
Read-only

Which x402 API should I call for this task? Searches the Coinbase Bazaar catalog and ranks candidates by evidence of real use: distinct payers, repeat calls per payer, recency of payments and price. Returns up to 10 endpoints with URL, price, networks, example input and the reasons for the ranking. Price: $0.01 USDC per call (x402).

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": {
      "need": "<need>"
    },
    "name": "x402_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesTask in plain words
limitNoResults to return, 1-10 (default 5)
networkNoCAIP-2 network filter, e.g. eip155:8453 (optional)
max_priceNoMaximum USD price per call (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds genuinely useful behavior beyond that: a result cap of 10, the ranked-by-evidence model, the returned fields, and a concrete cost of $0.01 USDC per call via x402. The paid-call disclosure is exactly the kind of context annotations cannot convey.

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?

Three short sentences with the use case front-loaded, followed by mechanics and then cost. Covers a lot with little waste; minor redundancy between 'up to 10 endpoints' and the limit parameter.

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?

There is no output schema, and the description compensates well by enumerating the returned fields and the ranking rationale, plus the per-call price. What remains unstated, such as pagination or empty-result behavior, is minor for a 4-parameter ranked search.

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 coverage is 100%, so every parameter is already documented, making 3 the baseline. The description corroborates the limit ceiling of 10 and implies that price and network matter to ranking and filtering, but adds no format or syntax detail beyond the schema.

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 opens with the exact question the tool answers and then names the specific verb and resource: searching the Coinbase Bazaar catalog and ranking candidate x402 endpoints. It also states the ranking signal set (distinct payers, repeat calls, recency, price), which is far more than a restatement of the name.

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 leading 'Which x402 API should I call for this task?' frames the use case clearly, so an agent knows to call it when hunting for an x402 endpoint. However, no alternatives are named and no when-not condition is given, so routing is implied rather than explicit.

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

All Tlacuilo 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