Skip to main content
Glama

search_help

Read-onlyIdempotent

Search the Bookatu help centre, the plain-language guides to every feature, in any of its 14 languages. Returns the guides that match, closest first, with their summary, page, markdown copy and the dashboard screen each is set up on.

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_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. How many guides, 1 to 10. Default 5.
queryYesWhat you want to know, in your own words, e.g. "how do I take a deposit".
languageNoOptional. The language to search and answer in: en, de, fr, es, it, nl, pt, da, sv, nb, fi, pl, ja, cs (a tag like de-DE works too). Defaults to English; a language Bookatu has no catalog for reads English. The question itself may be written in any of these languages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds meaningful context on top: results are ranked 'closest first', each carries summary, page, markdown copy and dashboard screen, and queries in a language with no catalog fall back to English. What is missing is anything about result limits or empty-result behavior, but the disclosure of return shape and ranking is well beyond the annotations.

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, front-loaded with the action and resource, then the return contract. Dense but every clause carries information; the only slack is the slightly run-on second sentence listing return fields.

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?

With no output schema, the description correctly takes on the job of explaining what comes back and in what order, and the language fallback behavior is covered. What it lacks is the workflow hint about what to do with the returned page/markdown versus calling get_help_article, a minor gap for a read-only search tool with fully documented parameters.

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 query, limit and language are already documented in detail, including the same English-fallback rule the description mentions. The description only adds the count of 14 languages and the natural-language framing, which is marginal uplift over the schema.

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 and resource ('Search the Bookatu help centre, the plain-language guides to every feature') plus the scope of 14 languages, which is enough to distinguish it from search_blog and search_developer_docs by subject matter. It stops short of naming those siblings explicitly, so differentiation is inferred from the resource name rather than stated.

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 'help centre ... guides to every feature', suggesting product how-to questions rather than blog or API content. There is no explicit when-to-use statement, no exclusions, and no pointer to get_help_article for fetching a specific guide once a search result is chosen.

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