Skip to main content
Glama

Find seller

find_seller
Read-only

WHO CAN DO THIS FOR ME? Say what you need ("weather forecast", "translate to Spanish", "image generation") and, if you like, the most you will pay per call. Returns up to 10 paid x402 services you can pay right now, best payment record first: what each does, the endpoint to call, its price, the wallet to pay (USDC on Base) and the check_payment verdict for it. The ones after the first are backups, each a different seller. Only services that answered a check in the last 3 days asking to be paid at their own wallet are shown, and none the payment check stops. Rank is never for sale. Free, no key.

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": "find_seller"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesWhat the service should do, in a few words.
limitNoOptional: how many sellers, 1 to 10 (5 if left out).
max_price_usdNoOptional: the most you will pay per call, in US dollars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the read-only, non-destructive safety profile, and the description adds substantial behavior beyond them: a cap of 10 results, ranking by payment record, USDC-on-Base wallets, a freshness filter of three days, exclusion of anything the payment check rejects, and the guarantee that rank is not purchasable. It also states that no key or payment is required to call it. This is rich, decision-relevant context.

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?

It is front-loaded with the user-facing question and the core instruction, then layers on return details and filtering rules. Most sentences earn their place, though the freshness sentence ('answered a check in the last 3 days asking to be paid at their own wallet') is dense and slightly convoluted.

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?

No output schema exists, so the description must explain returns, and it does: what each service does, the endpoint, price, wallet, and the check_payment verdict. It also explains the ordering and backup semantics. It does not state what happens when there are zero matches, which is the only notable gap for a three-parameter discovery tool.

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 need, limit, and max_price_usd are already documented in the input schema, including the 1–10 range and default of 5. The description restates the price ceiling in plainer language ('the most you will pay per call') but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb-and-resource framing: describe a need, optionally a max price per call, and receive up to 10 paid x402 services you can pay right now. It is clearly distinct from payment/deal siblings because it is a discovery tool that returns endpoints and prices. It stops short of naming a sibling such as search_bots, so an agent must infer the boundary itself.

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

Usage Guidelines4/5

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

It supplies clear context: use this when you need a service to do something and want sellers you can pay immediately, with an optional price ceiling. It also implies the results are actionable only for the first entry, with the rest as backups. There are no explicit exclusions or named alternatives, which keeps it below a 5.

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.

Resources