Skip to main content
Glama

compare_plans

Read-only

Side-by-side diff of two HelloBooks tiers (e.g. "Pro vs Business"). Pass planA, planB (free/starter/pro/business/scale/cpa) and an optional country. Returns each plan’s monthly + annual price, AI credit allowance and transaction limit, the monthly/annual price delta (B minus A) and which is cheaper, plus the features shared, only in A, and only in B. Prices are live-fed via list_plans; feature diff is over published bullets — confirm specifics with list_features.

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": {
      "planA": "<planA>",
      "planB": "<planB>"
    },
    "name": "compare_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
planAYesFirst plan tier to compare.
planBYesSecond plan tier to compare.
countryNoISO country code for local pricing + region features. Omit for USD/default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/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 genuinely useful context beyond that: prices are live-fed, the feature diff is over published bullets only (an accuracy caveat), and the delta is computed B minus A. It does not cover pagination or response shape, but for a read-only comparison tool this is adequate.

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, then inputs, then return contents, then a caveat — a logical order with no filler. The single dense sentence listing return fields is long but each element is informative.

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 carries the return-value burden and does so thoroughly: prices (monthly and annual), AI credits, transaction limits, delta direction, cheaper plan, and the three feature buckets. Nothing an agent needs to call or interpret the result is missing.

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 all three parameters carry enum values plus descriptions, so the schema does the heavy lifting. The description restates the plan tiers and the optional country but adds little beyond what the schema already says about country affecting local pricing and region features.

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 ('Side-by-side diff of two HelloBooks tiers') with a concrete example ('Pro vs Business'), and the enumerated plan tiers make the scope unambiguous. An agent can distinguish it from list_plans and list_features without opening any 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 names the two required inputs and the optional country, and routes the agent to siblings: prices come live via list_plans and feature specifics should be confirmed with list_features. It stops short of stating when NOT to use this tool (e.g. single-plan lookup), so it is clear context rather than full when/when-not guidance.

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