Skip to main content
Glama

estimate_annual_cost

Read-only

Itemized first-year cost of ownership from HelloBooks’ own published prices. Pass a core plan (free/starter/pro/business/scale), optional country, billing (annual|monthly, default annual), addOns (warehouse-addon/manufacturing-addon), and one-time creditPacks ([{id, quantity?}]). Returns line items, the plan/add-on annual cost, one-time credit-pack cost, totalFirstYear, and annualBillingSavings (saving vs paying monthly) in the country currency. An estimate from list prices, not a quote (taxes/discounts excluded) — confirm with list_plans / list_credit_packs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plan": "<plan>"
    },
    "name": "estimate_annual_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesCore plan tier to cost out.
addOnsNoStackable per-entity add-on modules to include.
billingNoBilling cadence (default annual). Annual is cheaper on paid tiers.
countryNoISO country code for local pricing. Omit for the USD/default list.
creditPacksNoOne-time AI credit packs to include (with optional quantity).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/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 adds real behavioral value beyond that: the return payload (line items, plan/add-on annual cost, one-time credit-pack cost, totalFirstYear, annualBillingSavings), currency derivation from country, and the caveat that figures exclude taxes and discounts. Only gaps are error/unsupported-country behavior and whether list prices are cached or live.

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?

Three dense sentences, front-loaded with purpose before inputs and caveats. The parameter enumeration in the first sentence is packed but functional; nothing is redundant with the title or annotations.

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?

With no output schema, the description carries the return-value burden and does so by naming each returned field and the currency rule. Combined with readOnly/openWorld annotations and a fully documented 5-parameter schema, an agent has enough to invoke and interpret it correctly; only failure modes are unexplained.

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%, with enums and defaults already documented, so the baseline is 3. The description restates the parameter set compactly and adds the useful note that results are returned in the country's currency, but it introduces no syntax or constraint detail the schema doesn't already carry.

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?

States a specific verb and resource: 'Itemized first-year cost of ownership from HelloBooks' own published prices,' with the exact inputs (plan, country, billing, addOns, creditPacks) enumerated. This clearly separates it from list_plans and list_credit_packs, which the description explicitly names as the catalog-lookup alternatives.

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?

The description frames the tool's role precisely — an estimate from list prices, not a quote, with taxes and discounts excluded — and routes the agent to list_plans / list_credit_packs for confirmation. It stops short of stating when to prefer it over compare_plans or compare_books_to_hellobooks, but the intended use case is unambiguous.

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