Skip to main content
Glama

HelloBooks AI Agents MCP Server

by io.github.HelloBooksAIAgents
OverviewDiscussionsAdmin

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). The 8 priced regions return local currency prices; other supported country hubs return the USD/default list price with pricingCountry=US fallback metadata. 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 any supported country ISO code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoRestrict the response to a single credit pack.
countryNoISO country code. Filters prices to one country. Countries without local pricing return the USD/default list price with fallback metadata. Omit to return priced markets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO country code. Filters prices to one country. Omit to return all 8 markets."New value: +"ISO country code. Filters prices to one country. Countries without local pricing return the USD/default list price with fallback metadata. Omit to return priced markets."
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "IN",
-  "US",
-  "CA",
-  "GB",
-  "AU",
-  "AE",
-  "SG",
-  "NZ"
-]New value: +[
+  "IN",
+  "US",
+  "GB",
+  "AU",
+  "AE",
+  "CA",
+  "SG",
+  "NZ",
+  "HK",
+  "DE",
+  "FR",
+  "NL",
+  "ES",
+  "IT",
+  "JP",
+  "KR",
+  "SA",
+  "IE",
+  "ZA",
+  "MY",
+  "PH",
+  "NG",
+  "KE",
+  "ID",
+  "TH",
+  "VN",
+  "PK",
+  "BD",
+  "BR",
+  "MX",
+  "AR",
+  "CL",
+  "CO",
+  "SE",
+  "NO",
+  "DK",
+  "FI",
+  "BE",
+  "AT",
+  "CH",
+  "PL",
+  "PT",
+  "CZ",
+  "RO",
+  "HU",
+  "GR",
+  "TR",
+  "UA",
+  "IL",
+  "EG",
+  "BG",
+  "HR",
+  "SI",
+  "SK",
+  "LT",
+  "LV",
+  "EE",
+  "RS",
+  "MA",
+  "QA",
+  "KW",
+  "JO",
+  "OM",
+  "BH",
+  "TN",
+  "DZ",
+  "GH",
+  "TZ",
+  "UG",
+  "ET",
+  "ZM",
+  "ZW",
+  "RW",
+  "SN",
+  "LK",
+  "NP",
+  "MM",
+  "KH",
+  "LA",
+  "PE",
+  "EC",
+  "BO",
+  "PY",
+  "UY",
+  "CR",
+  "PA",
+  "GT",
+  "DO",
+  "KZ",
+  "UZ",
+  "BY",
+  "MD",
+  "BA",
+  "MK",
+  "AL",
+  "LB",
+  "IQ",
+  "TT",
+  "MO",
+  "BN",
+  "CY",
+  "MT",
+  "LU",
+  "IS",
+  "ME",
+  "GE",
+  "AM",
+  "AZ",
+  "TM",
+  "TJ",
+  "KG",
+  "MN",
+  "CI",
+  "CM",
+  "TG",
+  "BJ",
+  "BF",
+  "ML",
+  "SL",
+  "LR",
+  "GN",
+  "MR",
+  "NE",
+  "TD",
+  "CD",
+  "CG",
+  "GA",
+  "MW",
+  "MZ",
+  "NA",
+  "BW",
+  "LS",
+  "SZ",
+  "MG",
+  "AO",
+  "MU",
+  "SC",
+  "CV",
+  "HN",
+  "SV",
+  "NI",
+  "JM",
+  "BB",
+  "GY",
+  "SR",
+  "FJ",
+  "PG",
+  "HT",
+  "BS",
+  "VE",
+  "IR",
+  "AF",
+  "SY",
+  "YE",
+  "LY",
+  "SD",
+  "SO",
+  "CU",
+  "KP",
+  "TW",
+  "PS",
+  "ER",
+  "DJ",
+  "SS",
+  "CF",
+  "GQ",
+  "BI",
+  "KM",
+  "ST",
+  "GW",
+  "EH",
+  "WS",
+  "TO",
+  "VU",
+  "SB",
+  "KI",
+  "TV",
+  "NR",
+  "PW",
+  "FM",
+  "MH",
+  "AG",
+  "LC",
+  "VC",
+  "KN",
+  "DM",
+  "GD"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that packs are one-time pay-as-you-go, stack on any plan including Free, and explains pricing behavior (8 priced regions return local currency, others fall back to USD with metadata). This is meaningful behavioral detail beyond the schema.

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?

The description is concise, front-loaded with the core purpose, and structured logically: purpose, details, usage guidance, and filtering. Every sentence contributes useful information without redundancy.

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 tool with two optional filter parameters and no output schema, the description covers purpose, usage context, behavioral nuances, and filtering expectations. It even references the schema's 'country' fallback behavior, making it complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds semantic value by mapping 'boost / power / mega / ultra' to credit amounts (5,000, 15,000, 50,000, 150,000) and clarifying the 'country' parameter's fallback behavior. This enriches what the schema alone provides, justifying a score above the 3 baseline.

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 tool lists HelloBooks AI credit packs and provides specific sizes (Boost 5,000, Power 15,000, etc.). It distinguishes this tool from siblings like list_plans by focusing on one-time top-ups rather than subscription 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?

It explicitly says 'Use this when a user asks how to buy more AI credits or top up after exhausting a plan allowance.' This gives clear context for when to call the tool. It doesn't name alternative tools, but none of the siblings directly cover credit packs, so no exclusion is necessary.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources