Skip to main content
Glama

feature_search

Read-only

Free-text search across the marketing feature catalog, plan features, integrations, country features, compliance frameworks, competitor positioning, statutory deadlines, local payment methods, and published articles on hellobooks.ai. Queries like "vs Xero", "QuickBooks alternative", "GSTR-3B due", "UPI invoice", "1099 article", or "agentic accounting" surface the matching entry near the top.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (default 20).
queryYesFree-text query, e.g. "BAS lodgement", "multi-currency", "vs QuickBooks", "GSTR-3B due", or "UPI invoice cap".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 does add real behavioral context beyond that: the corpus is unusually broad (marketing copy, competitor positioning, statutory deadlines, articles) and results are relevance-ranked ("surface the matching entry near the top"). It stops short of saying whether matching is keyword vs fuzzy, so it stops at a solid 3.

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?

Two sentences, purpose first and examples second, so the key information is front-loaded. The example list in sentence two is long but each item maps to a distinct corpus, which justifies most of the length.

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?

A simple one-required-string tool with full schema coverage and clear read-only annotations; the main thing an agent needs, the breadth of what is searchable, is present. The remaining gap is sibling routing against `search`/`list_features`, but no output schema means return-value documentation is correctly absent.

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% and both parameters (query, limit) are documented inline with ranges, defaults, and examples. The description's example queries reinforce the same idea but add no syntax or matching rules the schema does not already give, so the baseline 3 applies.

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?

States a specific verb (free-text search) and a concrete, enumerated set of corpora (feature catalog, plan features, integrations, compliance frameworks, statutory deadlines, articles). An agent knows exactly what this searches, though it never contrasts itself with the sibling `search` tool, so the boundary is left to inference.

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 only implied: the example queries ("vs Xero", "GSTR-3B due", "UPI invoice") show when it is appropriate, but there is no explicit when-to-use/when-not statement and no alternative named, even though `search` and `list_features` look adjacent.

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