Skip to main content
Glama

APIHub

by io.apihub.mcp

apihub_call_external

Call an external x402-protected URL (any provider in the marketplace or any x402 API). APIHub pays the provider on your behalf using the platform wallet and debits your credit balance for the exact amount. No wallet or gas required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe full URL to call (e.g. https://hub.atxp.ai/...)
bodyNoRequest body (object or string). Omit for GET.
methodNoHTTP method (default POST)
headersNoAdditional request headers. Do not set Authorization or X-PAYMENT - handled automatically.

TDQS

A4/5.0
Behavior5/5

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

Despite no annotations, the description provides key behavioral details: payment handled via platform wallet, credit balance debited, no wallet/gas needed, and automatic header handling (do not set Authorization/X-PAYMENT). This fully discloses important behavioral traits.

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?

Two sentences that are front-loaded with the core purpose. No unnecessary words. Every sentence adds value.

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?

The description covers the payment model and parameter constraints adequately for the tool's complexity. It could optionally mention error behavior or usage limits, but overall it is sufficient for an agent to understand the tool's function.

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% with descriptions. The description adds some value by reiterating header restrictions and payment context, but it largely restates schema fields. It does not add new meaning beyond what the schema provides.

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 clearly states the tool calls an external x402-protected URL and handles payment on behalf. However, it doesn't differentiate from the sibling tool 'apihub_call' which might have similar functionality, so more explicit distinction would improve clarity.

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 description says to use for external x402-protected URLs and any provider/marketplace API. It does not specify when not to use it (e.g., for internal calls) or mention alternatives, leaving some ambiguity about context.

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