Skip to main content
Glama

Search HelloBooks public knowledge

search
Read-only

Search the HelloBooks public knowledge base and return citable document ids. Covers pricing plans, AI credit allowances, integrations, per-country features and compliance frameworks, statutory filing deadlines, local payment methods, competitor positioning, the marketing feature catalog, and published articles on hellobooks.ai. Returns { results: [{ id, title, url }] }; pass an id to fetch for the full document. No customer or account data is reachable through this server.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (default 10).
queryYesNatural-language query, e.g. "HelloBooks GST filing for India" or "pricing vs Xero".

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish read-only and closed-world behavior, and the description adds meaningful scope context by stating that no customer or account data is reachable. It also discloses the result shape and the follow-up fetch workflow, though it does not mention ranking, pagination, or rate limits.

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?

The description is front-loaded with the core action and remains compact, with each sentence serving purpose, scope, return workflow, or data boundary. The coverage list is long but helps an agent decide whether this search spans the needed topics.

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?

For a simple two-parameter search tool with an output schema, the description provides enough context: scope, return format, fetch follow-up, and data boundary. The main missing piece is explicit routing against the many specialized retrieval siblings.

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%, so the query and limit parameters are already well documented with examples and constraints. The description does not add parameter-specific meaning beyond what the schema provides, which is acceptable at the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: search the HelloBooks public knowledge base and return citable document ids. It clearly scopes the content covered, but it does not explicitly differentiate this broad search from specialized siblings such as list_plans, compliance_deadlines, or feature_search.

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?

Usage is implied by the broad knowledge-base scope, and the description correctly routes the agent to fetch for full documents using an id. However, it gives no explicit when-to-use guidance versus the many specialized sibling tools, nor any when-not-to-use conditions.

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