compliance_capabilities
Return supported compliance frameworks for a country (BAS, STP, GST, MTD, 1099, etc.) with version and certification info.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| country | Yes | Required ISO country code. |
HelloBooks AI Agents MCP Server
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool returns frameworks with version and certification info, implying a read-only query. However, it could explicitly state that it is safe and idempotent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no unnecessary words. It starts with the verb 'Return' and immediately conveys the tool's purpose. Every part is informative and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has only one parameter and no output schema, the description provides enough context by specifying what is returned (frameworks with version and certification info). It could be improved by detailing the response format or listing all possible framework values, but it is sufficient for a simple lookup tool.
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%, providing the parameter description as 'Required ISO country code' with enum values. The description adds value by explaining that the country parameter is used to return specific frameworks, which goes beyond the schema's structural definition.
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?
The description clearly states the tool returns supported compliance frameworks for a country, listing examples (BAS, STP, GST, etc.) and mentions version and certification info. It distinguishes from siblings like compliance_deadlines by focusing on listing available frameworks rather than deadlines.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when needing to retrieve compliance frameworks for a specific country, but does not explicitly state when to use this tool over alternatives like compliance_deadlines or country_support. No exclusion criteria or context for when not to use it.
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.
TDQS
A3.8/5.0
Disambiguation4/5
Tools are largely distinct, each targeting a specific report type (balance sheet, P&L, trial balance) or functionality. Some overlap exists between QBO and Xero variants, but descriptions clearly differentiate them. Overall, an agent can reliably select the right tool.
Naming Consistency4/5
Most tools follow a consistent snake_case verb_noun pattern (e.g., analyze_balance_sheet, list_articles). A few exceptions like free_tier_eligibility and how_munimji_helps break the pattern but are still readable and predictable.
Tool Count3/5
With 29 tools, the count is on the higher side but justified by the domain's breadth (financial analysis, compliance, migration, pricing, etc.). Some reduction through parameterization (e.g., merging QBO/Xero variants) would improve scope.
Completeness4/5
The tool surface covers key areas: financial statement analysis, compliance, migration estimation, feature/pricing info, and partner programs. Missing are direct data manipulation tools (e.g., create/edit journal entries), which may be intentional for a read-only analysis agent.