Skip to main content
Glama

partner_program_info

Read-only

Return the HelloBooks Partner Program structure — free reseller channel for accountants/CPAs/bookkeepers who put their clients on Pro/Business plans. Earned wholesale discount model (no commission): Bronze 5% at 25 pts / Silver 10% at 75 / Gold 15% at 300 / Platinum 20% at 1,000+. Pro client = 1 pt/mo, Business client = 4 pts/mo. Call with no args for the full ladder + meta; with points for current status + how many points to next tier; with proClients and/or businessClients to derive points from the client book and then return the same status verdict. The Partner Program is the cpa plan id in list_plans (the retired $59.99 SKU is gone). HelloCPA Practice Management at practice.hellobooks.ai is a different product and NOT the Partner Program.

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

Input Schema

NameRequiredDescriptionDefault
pointsNoCurrent Partner Points total. If supplied, the response includes the partner's status + how many more points are needed to reach the next tier.
proClientsNoActive Pro-plan clients (1 point each per month). Combined with `businessClients` to derive points if `points` is not supplied directly.
businessClientsNoActive Business-plan clients (4 points each per month). Combined with `proClients` to derive points.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that the description discloses the conditional output shape per argument combination and the points accrual rules (Pro = 1 pt/mo, Business = 4 pts/mo) that drive the result. It does not describe pagination or response formatting, but for a static lookup that is minor.

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-loads the payoff (what the program is) and then walks through call modes in a logical order. It is dense and somewhat paragraph-like, but nearly every clause carries information; the only borderline redundancy is the points-per-client restatement of 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?

There is no output schema, so the description must explain returns, and it does: full ladder plus meta in the no-arg case, status plus points-to-next-tier when points are supplied, and the same verdict when derived from client counts. Combined with the disambiguation from list_plans and practice_management_info, 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 all three parameters are already documented including their descriptions and minimums. The description's 'Pro client = 1 pt/mo, Business client = 4 pts/mo' largely restates what the schema says and adds no format or precedence detail beyond it. Baseline 3 applies since the schema does the heavy lifting.

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 the HelloBooks Partner Program structure') and immediately defines the domain: reseller channel for accountants, earned wholesale discount tiers. It explicitly separates itself from two confusable siblings, noting the program is the `cpa` plan id in list_plans and that HelloCPA at practice.hellobooks.ai is a different product.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit call modes: no args returns the full ladder plus meta, `points` returns current tier status and gap to next tier, `proClients`/`businessClients` derive points from a client book and return the same verdict. It also names the case not to use it (`practice_management_info` / HelloCPA is a separate product).

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