Skip to main content
Glama

practice_management_info

Read-only

Return HelloCPA Practice Management info — the standalone product at practice.hellobooks.ai for running a CPA / CA / bookkeeping practice (proposals + CPQ, workflow, time tracking, billing, 6-role RBAC, Gmail/Outlook/Calendar sync, CSV migration from TaxDome / Karbon / Canopy). NOT the Partner Program and NOT a tier in list_plans. Per-user pricing model — US shipped at $9.99/user/month (free up to 2 users + 10 clients, 90-day trial, enterprise at 50+ users). 7 other markets (IN, GB, AU, CA, AE, SG, NZ) are roadmap as of 2026-06-12. Call with no args for the full 8-region matrix + features + meta, or with country for one region's status + pricing + competitor frame.

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

Input Schema

NameRequiredDescriptionDefault
countryNoISO country code. Omit to get the full 8-region matrix. US is shipped; the other 7 are roadmap as of 2026-06-12.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/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 substantive context beyond that: it states data freshness (roadmap as of 2026-06-12), discloses the returned payload shape (region matrix, features, meta, competitor frame), and summarizes the pricing model and trial terms. It stops short of describing response size or pagination, but nothing is contradicted.

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 identity and the sibling exclusions, then the invocation modes. It is dense and fairly long, and the parenthetical feature list plus per-user price figures ($9.99/user/month, free tier, 90-day trial, enterprise at 50+) are somewhat marketing-flavored, but each still conveys content the agent will receive back.

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?

For a one-parameter read-only info tool with no output schema, the definition covers identity, exclusions, both invocation modes, freshness, and a preview of returned fields. Nothing an agent needs in order to call it correctly is missing.

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% and the enum is already documented, so the baseline is 3. The description earns above baseline by explaining the behavioral difference between omitting the parameter (full 8-region matrix) and supplying it (one region's status + pricing + competitor frame), which the schema does not convey.

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?

Names a specific resource (HelloCPA Practice Management info) and immediately scopes it: the standalone product at practice.hellobooks.ai covering proposals/CPQ, workflow, time tracking, billing, RBAC, sync, and migration. It explicitly excludes two confusable siblings — the Partner Program and any tier in list_plans — so an agent can route without opening another schema.

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 invocation guidance: no args for the full 8-region matrix plus features and meta, or `country` for a single region's status, pricing, and competitor frame. Combined with the two explicit exclusions (partner_program_info, list_plans), the when-to-use and when-not-to-use conditions are both stated.

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