Skip to main content
Glama

HelloBooks AI Agents MCP Server

free_tier_eligibility

Read-only

Return the HelloBooks Free-plan annual-invoice-turnover thresholds for the 8 priced markets (IN ₹40 lakh / US $100K / GB £90K / AU A$75K / CA C$30K / NZ NZ$60K / SG S$1M / AE AED 375K). Free includes one-time free AI credits with no published number, plus up to 200 transactions per year; per-entity invoice turnover above the country cap forces an upgrade to Pro or Business. Call with no args to get the full table, with country for one threshold, or with country AND annualInvoiceRevenue (in the country currency, NOT USD-equivalent) for a freeEligible verdict with headroom math. Bank-feed total and cash receipts are explicitly NOT used for the turnover cap.

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": "free_tier_eligibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoISO country code of the entity. Omit to return the full 8-country threshold table.
annualInvoiceRevenueNoAnnual invoice turnover for the entity, in its home currency (NOT USD-equivalent). Only used when `country` is also provided — the tool then returns a `freeEligible` verdict. Bank-feed total and cash receipts are explicitly NOT used by the gate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 safety is covered. The description adds genuinely useful behavioral context beyond that: thresholds are per-country caps, exceeding them forces an upgrade to Pro or Business, input must be in home currency not USD-equivalent, and certain revenue sources are excluded. No contradiction with 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 purpose and the market table, then the call modes. The parenthetical list of eight thresholds is dense but high-value. There is minor redundancy, since the bank-feed/cash-receipts exclusion appears in both the description and the schema.

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?

Although there is no output schema, the description spells out all three return shapes: full table, single threshold, and a `freeEligible` verdict with headroom math. Combined with the currency and exclusion rules, an agent has everything needed to call it correctly.

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 coverage is 100%, so both parameters are already documented, including the enum and the 'only used when country is provided' conditional. The description restates the currency caveat and the bank-feed exclusion rather than adding new parameter meaning, so the baseline 3 applies.

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: return HelloBooks Free-plan annual-invoice-turnover thresholds for 8 named priced markets, and even enumerates the caps. An agent can immediately tell this is a plan-limit lookup, distinct from siblings such as compare_plans or estimate_annual_cost.

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 describes three call modes: no args for the full table, `country` alone for one threshold, and `country` + `annualInvoiceRevenue` for a `freeEligible` verdict. It also states the exclusion that bank-feed totals and cash receipts do not count. It stops short of naming a sibling alternative for broader plan comparison, which keeps it below a 5.

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.