Read-only. Returns your current APIHub credit balance (in microdollars and USD), total lifetime spending (microdollars and USD), and total completed request count. Requires a valid API key. Use before apihub_call or apihub_call_external to confirm sufficient funds for a paid request, or periodically to audit usage. Does not modify state, send payments, or call upstream APIs; for top-ups use apihub_topup.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully discloses behavior: read-only, no state changes, no payments, no upstream calls. Comprehensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with 'Read-only.' No wasted words, efficiently conveys all necessary information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, description fully explains what the tool returns and mentions required API key. Complete for a zero-param tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters; description adds value by detailing the response contents (balance in microdollars and USD, lifetime spending, request count). Exceeds baseline for zero-param tools.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it returns credit balance, lifetime spending, and request count. Distinguishes from sibling tools like apihub_call and apihub_topup by specifying when to use each.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly tells when to use (before paid requests), what it does not do (no modifications, no payments), and names alternatives (apihub_topup for top-ups).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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).
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.
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.
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.