Skip to main content
Glama

search_blog

Read-onlyIdempotent

Search the Bookatu blog for business owners (a translated post in the language asked for), or the engineering blog with section "engineering". Returns the posts that match, closest first, with their excerpt, date, page and markdown copy.

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

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. How many posts, 1 to 10. Default 5.
queryYesWhat you are looking for, e.g. "reduce no-shows".
sectionNoOptional. "blog" (the default) or "engineering".
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.

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), so the bar is lower. The description still adds real value beyond them: results are ranked 'closest first' and each result carries excerpt, date, page and markdown copy, plus the notable behavior that a post is returned translated into the requested language.

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 search scope and followed by the return shape; nothing is filler. The parenthetical about translated posts is slightly awkwardly placed but still earns its space by flagging language behavior.

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 compensates by naming the returned fields and the ordering, which is what an agent needs to decide whether to call it. Remaining gaps are minor: no pagination note and no explicit statement of what an empty result looks like.

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%, so the schema already documents limit, section and language in detail; baseline 3 applies. The description reinforces the language parameter's translation semantics and the section routing, but adds little syntax or edge-case detail (e.g. limit behavior when fewer posts match) beyond the schema text.

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+resource ('Search the Bookatu blog') and clarifies the two corpora (business-owner blog vs. engineering blog via section='engineering'), which an agent cannot infer from the name alone. It stops short of distinguishing itself from the sibling get_blog_post, which fetches a single post, so the boundary between searching and retrieving is left implicit.

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?

Useful routing guidance is embedded in the description: pass section 'engineering' to hit the engineering blog, otherwise the business-owner blog. There is no explicit when-to-use/when-not guidance and no mention of get_blog_post as the alternative for fetching a known post, so the agent must infer the split.

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