Skip to main content
Glama

APIHub

by io.apihub.mcp

apihub_list_services

Read-only. Lists onboarded APIHub services alphabetically, returning each service's slug, name, description, category, provider, endpoint count, and lowest per-endpoint price in microdollars. No authentication required. Use this to browse the full onboarded catalog when you don't have a specific capability in mind; prefer apihub_search when filtering by query, category, or price. Does not include external x402 APIs (use apihub_search_external for those) and does not return endpoint-level details (use apihub_get_service for that).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoOptional max number of services to return. Default 20, minimum 1, hard cap 100. Values above 100 are clamped.

TDQS

A4.9/5.0
Behavior5/5

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

Discloses read-only nature and no authentication required. Describes clamping behavior for limit parameter. States what is not included (external x402 APIs, endpoint details).

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 sentences, front-loaded with action and key details. No redundant information. Efficient use of words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one optional parameter and no output schema, the description is comprehensive, covering purpose, return fields, usage guidance, and behavioral constraints.

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 limit parameter fully (100% coverage). Description adds clamping behavior beyond schema, which is valuable for correct usage.

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?

Clearly states it lists onboarded APIHub services alphabetically with specific return fields. Distinguished from siblings (apihub_search, apihub_search_external, apihub_get_service).

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?

Explicitly provides when to use (browsing full catalog without specific capability) and when not to use (filtering, external APIs, endpoint details). Names alternatives: apihub_search, apihub_search_external, apihub_get_service.

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

All APIHub toolsInspect
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