Skip to main content
Glama

Mozaika Books Catalog

search_books

Search the Mozaika Publications romance catalog and published "books like" hub pages. Returns Mozaika works (title, author, URL, tropes, reader promises, series status) and matching comparison hubs and reading guides. Publisher-run; includes outside read-alikes on hub pages but no purchase links.

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

Input Schema

NameRequiredDescriptionDefault
langNoLocale code (default en).
limitNoMax works to return (default 10).
queryYesTrope, mood, title fragment, or "books like …" phrase.

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?

With no annotations, the description carries the burden and does disclose meaningful traits: it is publisher-run, results include comparison hubs and reading guides with outside read-alikes, and there are no purchase links. It also names the exact fields returned, which is more than the schema provides. It stops short of stating that it is read-only, whether limit is paginated or truncated, or any access constraints.

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?

Three short sentences, front-loaded with the scope and the return contents, with no filler. The final sentence is telegraphic ('Publisher-run; includes outside read-alikes on hub pages but no purchase links') and takes a re-read, but every clause contributes information.

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 3-parameter, annotation-free, output-schema-free search tool, the description covers scope, source, and return shape well. What is missing is sibling disambiguation against books_like and any note on result truncation or read-only behavior — gaps that matter for correct tool selection rather than for calling the tool.

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 schema already documents query, lang, and limit with defaults and bounds; baseline is 3. The description adds no parameter-level detail beyond the schema — it never explains how query is matched (exact vs. substring vs. semantic) or what happens when limit truncates results.

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 Mozaika Publications romance catalog plus 'books like' hub pages, and enumerates the returned fields (title, author, URL, tropes, reader promises, series status). An agent can tell this is a catalog search rather than a single-book fetch or a trope listing, though it never contrasts itself with the books_like sibling that overlaps its 'books like …' query space.

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 query semantics (trope, mood, title fragment, or 'books like …' phrase) suggest when the tool fits, but there is no explicit when-to-use/when-not statement and no routing to books_like, get_book, or list_tropes. Given a sibling literally named books_like and a query mode that accepts 'books like …' phrases, the absence of a disambiguation rule is a real gap.

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