Skip to main content
Glama

x402Fi

Search x402Fi services

search_services
Read-onlyIdempotent

Search the paid x402 APIs listed on x402Fi (Robinhood Chain, priced per call in USDG). Every word of the query must match. Returns endpoints with their price, method and payee name; use get_listing for how to call one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10.
queryNoKeywords, e.g. 'stock risk' or 'rug check'. Omit to list everything.
categoryNoExact category, e.g. 'AI & agents' or 'Developer tools'.
max_price_usdNoOnly endpoints whose price (or price ceiling) is at most this, in USD, e.g. '0.05'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), so the bar is lower. The description adds real behavior beyond them: the AND-matching rule for query words and the exact shape of returned records (price, method, payee name). It omits ranking/ordering behavior, which keeps it short of a 5.

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?

Three short, front-loaded sentences with no filler: identity and domain first, matching rule second, return shape plus handoff last. Every clause carries information an agent would otherwise have to guess.

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?

With no output schema, the description usefully names the returned fields (price, method, payee) so the agent knows what comes back. It doesn't cover result ordering or whether limits truncate results, a minor gap for a simple read-only 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 description coverage is 100%, so all four parameters (limit, query, category, max_price_usd) are already documented, giving a baseline of 3. The description adds only the AND-semantics of query words and does not clarify category exactness or the price-ceiling behavior beyond what the schema states.

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?

States a specific verb (Search) and resource (paid x402 APIs listed on x402Fi), plus the domain context of Robinhood Chain and USDG per-call pricing. It distinguishes itself from get_listing by scoping itself to discovery rather than invocation.

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?

Explicitly routes the agent onward: "use get_listing for how to call one" gives a clear condition for switching siblings. It does not spell out when-not to use this tool, but for a search entry point the implied usage is unambiguous.

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.