Skip to main content
Glama

HelloBooks AI Agents MCP Server

by io.github.HelloBooksAIAgents

list_credit_packs

List HelloBooks AI credit packs — one-time pay-as-you-go top-ups (Boost 5,000, Power 15,000, Mega 50,000, Ultra 150,000 credits) priced in 8 regional currencies (USD, INR, CAD, GBP, AUD, AED, SGD, NZD). Credit packs stack on any plan, including Free. Use this when a user asks how to buy more AI credits or top up after exhausting a plan allowance. Filter by id (boost / power / mega / ultra) or country (ISO code).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoRestrict the response to a single credit pack.
countryNoISO country code. Filters prices to one country. Omit to return all 8 markets.

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided; description covers stacking behavior and filtering but lacks explicit safety or return format details. Adequate but not exhaustive.

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 with purpose front-loaded and no wasted words.

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?

No output schema, but description provides enough context for a simple list operation; could mention response shape but not critical.

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 coverage 100%; description adds meaning by explaining enum values (boost/power/mega/ultra) and country code usage beyond the schema descriptions.

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?

Describes specific verb 'list' and resource 'credit packs', names the packs and currencies, and distinguishes from sibling tools like list_plans.

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 states when to use: when user asks about buying credits or topping up. No when-not-to-use, but context is clear.

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

All HelloBooks AI Agents MCP Server 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

A3.8/5.0
Disambiguation4/5

Tools are largely distinct, each targeting a specific report type (balance sheet, P&L, trial balance) or functionality. Some overlap exists between QBO and Xero variants, but descriptions clearly differentiate them. Overall, an agent can reliably select the right tool.

Naming Consistency4/5

Most tools follow a consistent snake_case verb_noun pattern (e.g., analyze_balance_sheet, list_articles). A few exceptions like free_tier_eligibility and how_munimji_helps break the pattern but are still readable and predictable.

Tool Count3/5

With 29 tools, the count is on the higher side but justified by the domain's breadth (financial analysis, compliance, migration, pricing, etc.). Some reduction through parameterization (e.g., merging QBO/Xero variants) would improve scope.

Completeness4/5

The tool surface covers key areas: financial statement analysis, compliance, migration estimation, feature/pricing info, and partner programs. Missing are direct data manipulation tools (e.g., create/edit journal entries), which may be intentional for a read-only analysis agent.

Resources