APIHub

apihub_search

Read-only. Searches onboarded APIHub services by free-text query, with optional category, price, and type filters. Returns up to 10 matches ranked by uptime and endpoint count, each with slug, description, endpoints array, min price in microdollars, provider name, and quality score. No authentication required. Use this when you need to find an API by capability; use apihub_list_services to browse without a query, apihub_search_external to include the external x402 catalog, or apihub_get_service when you already know a slug. Does not call any upstream API or debit credits.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Optional filter. 'api' = standard REST APIs, 'content' = content gateways that proxy a fixed upstream URL.
`query`	Yes	Required free-text query matched against service name and description (case-insensitive substring match). Use 1-3 keywords describing the capability you want, e.g. 'weather' or 'stock price'.
`category`	No	Optional exact-match filter. Valid values: ai, data, search, finance, media, infra, communication, content, travel.
`max_price_microdollars`	No	Optional upper bound on price per request in microdollars (1 USD = 1,000,000 microdollars, so 10000 = $0.01). Services whose cheapest endpoint exceeds this are excluded.

TDQS

A4.5/5.0

Behavior4/5

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

Without annotations, the description covers safety (read-only), authentication (none), and side effects (no upstream calls, no credits). It also explains ranking criteria and return fields. Missing details on rate limits or pagination beyond 'up to 10 matches'.

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?

The description is a single paragraph but logically flows from purpose to inputs, output, auth, and usage context. It is informative without redundancy, though could be slightly more structured with bullet points.

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?

Given no output schema, the description adequately lists return fields and ranking. It covers essential context like no auth and no credit debit. Missing details on error handling or empty results, but overall sufficient for a search tool.

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?

Schema covers 100% of parameters with descriptions, and the description adds practical context: query is case-insensitive substring, max_price example conversion, and type enumeration explanation. This enhances understanding 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 clearly states the verb 'searches' and the resource 'onboarded APIHub services', and specifies the free-text query with optional filters. It distinguishes from sibling tools by naming alternatives, making the purpose unmistakable.

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

Usage Guidelines5/5

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

The description explicitly advises when to use this tool ('when you need to find an API by capability') and when to use alternatives (browse without query, include external catalog, or get by slug). This provides clear decision guidance.

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

All APIHub tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: balance checking, service discovery (list/search/get), paid calls (internal/external), content reading, and credit top-up. Overlaps like list_services vs. search are clearly differentiated by how they are used (browse vs. filter).

Naming Consistency5/5

All tools follow a consistent `apihub_verb_noun` pattern in snake_case. Verbs like get, list, search, call, topup are paired with appropriate nouns, and modifiers like 'external' are used uniformly.

Tool Count5/5

With 9 tools, the server is well-scoped for its purpose as an API marketplace. Each tool covers a necessary part of the workflow—discovery, payment, invocation—without unnecessary duplication or missing essentials.

Completeness5/5

The tool set provides a complete lifecycle: service discovery (list, search, get), credit management (balance, topup), and API invocation (call, call_external, read_content). No obvious gaps for the intended use case.

Resources

Need Help?