Skip to main content
Glama

recommend_plan

Read-only

Recommend the right HelloBooks tier for a business. Pass needs (free-text phrases like "GST filing", "multi-currency", "API access", "multi-entity", "payroll"), an optional estimatedAnnualTransactions, and an optional country for local pricing. Scores the core ladder (Free → Starter → Pro → Business → Scale) against the stated needs and transaction volume and returns the LOWEST-priced eligible tier that covers the most needs, plus the full ranked breakdown with matched/unmatched needs and per-tier price. Heuristic over published feature bullets, not a quote — confirm with list_plans / list_features. Add-ons and the free Partner Program are excluded from the core ladder.

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

Input Schema

NameRequiredDescriptionDefault
needsNoWhat the business needs, as free-text phrases, e.g. ["GST filing","multi-currency","API access","multi-entity","payroll"].
countryNoISO country code, for local pricing. Omit for the USD/default list.
estimatedAnnualTransactionsNoExpected ledger transactions per year. Above the Free cap (200) rules out Free.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a safe, closed-world lookup. Beyond that it adds real behavioral context: the selection rule (lowest-priced tier covering the most needs), the return shape (ranked breakdown with matched/unmatched needs and per-tier price), and the caveat that this is a heuristic rather than a binding quote. It does not mention determinism, tie-breaking, or what happens when needs is empty, though these are minor for a read-only recommender.

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 purpose, then inputs, then return behavior, then caveats and exclusions — a logical order with no filler sentences. It runs long as one undivided block, so structure could be improved with lighter formatting, but every sentence carries information an agent needs.

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?

No output schema exists, and the description compensates by describing the return payload (lowest eligible tier, ranked breakdown, matched/unmatched needs, per-tier price). All three parameters are documented, and the heuristic caveat plus ladder scope are stated, leaving nothing material missing for correct invocation.

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 is 100%, so the baseline is 3, but the description adds genuine meaning: it enumerates representative `needs` phrases, explains that `estimatedAnnualTransactions` gates the Free tier via the 200-transaction cap, and states that `country` selects local pricing versus the USD/default list. That is more than the schema's own field text provides.

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 ("Recommend the right HelloBooks tier for a business") and immediately scopes it against the plan-data siblings by calling itself a heuristic and naming list_plans / list_features as the confirmation path. An agent can distinguish it from compare_plans or list_plans 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?

Explicitly says when to route onward ("confirm with list_plans / list_features") and what this tool is not ("not a quote"), and it discloses exclusions (add-ons and the free Partner Program are out of the core ladder). It does not explicitly contrast with compare_plans or estimate_annual_cost, which would be the final piece for 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.

Resources