Skip to main content
Glama

list_plans

Read-only

List HelloBooks pricing plans with monthly + annual prices. The 8 priced regions return local currency prices (USD, INR, CAD, GBP, AUD, AED, SGD, NZD); other supported country hubs return the USD/default list price with pricingCountry=US fallback metadata while local books use the country currency. Covers the five-rung ladder — Free / Starter / Pro / Business / Scale — plus the free Partner Program (cpa plan id) and two per-entity stackable add-ons (Warehouse, Manufacturing). Returns AI credit allowance (monthly on paid plans; Free gets one-time starting credits that never refill — see aiCreditsNote), feature bullets, public signup URL, and live-feed/static-fallback provenance. Filter by plan (free / starter / pro / business / scale / cpa) or any supported country ISO code. HelloCPA Practice Management is a separate product on practice.hellobooks.ai — call practice_management_info, NOT this tool.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoRestrict the response to a single plan tier (`cpa` = free Partner Program). Countries without local pricing use the USD/default list price.
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. Changed3 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"
      +]
    • changedInput schema / properties / plan / description
      Previous value: -"Restrict the response to a single plan tier (`cpa` = free Partner Program). Starter and Scale are sold in the US only, so they return an empty price list for other countries."New value: +"Restrict the response to a single plan tier (`cpa` = free Partner Program). Countries without local pricing use the USD/default list price."
  2. Changed2 schema fields changed
    • changedInput schema / properties / plan / description
      Previous value: -"Restrict the response to a single plan tier (`cpa` = free Partner Program)."New value: +"Restrict the response to a single plan tier (`cpa` = free Partner Program). Starter and Scale are sold in the US only, so they return an empty price list for other countries."
    • changedInput schema / properties / plan / enum
      Previous value: -[
      -  "free",
      -  "pro",
      -  "business",
      -  "cpa"
      -]New value: +[
      +  "free",
      +  "starter",
      +  "pro",
      +  "business",
      +  "scale",
      +  "cpa"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / plan / description
      Previous value: -"Restrict the response to a single plan tier."New value: +"Restrict the response to a single plan tier (`cpa` = free Partner Program)."
    • changedInput schema / properties / plan / enum
      Previous value: -[
      -  "free",
      -  "pro",
      -  "cpa"
      -]New value: +[
      +  "free",
      +  "pro",
      +  "business",
      +  "cpa"
      +]
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description goes well beyond that by disclosing data provenance (live feed vs. static fallback), the USD/default list-price fallback with `pricingCountry=US` metadata for non-priced countries, and that Free-tier AI credits are one-time and never refill. These are non-obvious behaviors an agent cannot infer from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then layered detail, ending with the sibling exclusion — a sensible ordering. It is dense and long for a two-parameter list tool, and the country fallback rule is effectively stated three times (body plus both param descriptions), which is the main source of bloat.

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?

With no output schema, the description must carry the return shape, and it does: monthly and annual prices, AI credit allowance with a pointer to `aiCreditsNote`, feature bullets, public signup URL, and provenance flags. For a read-only, two-optional-param listing tool, nothing an agent needs to call it correctly is absent.

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 description coverage is 100% and both params are enums with documented values, so the baseline is 3. The description restates rather than extends the schema — the `cpa` = free Partner Program mapping and the "omit to return priced markets" rule both already appear in the parameter descriptions — though the enumerated list of eight priced regions adds a little practical clarity about which countries yield local currency.

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?

Opens with a specific verb and resource ("List HelloBooks pricing plans with monthly + annual prices") and immediately scopes the content: five plan tiers, the free `cpa` Partner Program, two stackable add-ons, and regional currency handling. It explicitly disambiguates from a different product's tool (practice_management_info), so an agent can distinguish it from siblings like compare_plans or estimate_annual_cost without opening a schema.

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?

Gives concrete selection guidance: filter by `plan` or `country`, omit `country` for priced markets, and a hard exclusion — "HelloCPA Practice Management is a separate product ... call `practice_management_info`, NOT this tool." What's missing is guidance against the closely related siblings compare_plans and estimate_annual_cost, which an agent could plausibly reach for instead of a raw plan listing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources