Skip to main content
Glama

HelloBooks AI Agents MCP Server

by io.github.HelloBooksAIAgents

list_features

List the full HelloBooks marketing feature catalog (145+ items). Filter by category, tier, status, marketedOnly, or substring query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNoFilter by the minimum plan tier / add-on that unlocks the feature.
limitNoMax number of features to return. Default 200.
queryNoOptional substring match against label + shortDescription.
statusNoFilter by rollout status. Defaults to all.
categoryNoFilter to one feature category (core-accounting, invoicing-billing, etc.).
marketedOnlyNoIf true, only return features marketed on the public website.

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must bear full burden. It states the tool lists features but does not disclose any behavioral traits such as read-only nature, rate limits, pagination behavior, or result ordering. For a list operation, the lack of idempotency/safety info is a gap.

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 two efficient sentences. The first declares purpose, the second lists filters. No fluff or repetition, front-loaded with the action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters and no output schema, the description covers filter options but omits output shape, pagination details, and default behavior of the limit parameter. Adequate for a simple list tool but could be more complete for agent decision-making.

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% with each parameter clearly described. The description repeats filter names but adds no extra meaning beyond what the schema provides. It does not explain filter combination logic (AND/OR) or defaults beyond schema hints.

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 verb 'list' and the resource 'full HelloBooks marketing feature catalog' with a specific item count, distinguishing it from sibling tools like 'feature_search' which likely targets specific features. The mention of filters further clarifies the scope.

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 lists which filters are available but gives no guidance on when to use this tool versus alternatives like 'feature_search' or 'list_feature_categories'. Usage context is implied through filter options, but explicit when-not/alternatives are missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HelloBooks AI Agents MCP Server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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.

Resources