Skip to main content
Glama

Mozaika Books Catalog

books_like

Find a published comparison hub for an outside book, show, author, or trope anchor, or a reading guide that answers a reader question (e.g. a dark romance series to binge). Returns Mozaika picks, vetted outside titles (text only), and the hub URL from Mozaika Publications.

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": {
      "title_or_show": "<title_or_show>"
    },
    "name": "books_like"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLocale code (default en).
title_or_showYesAnchor title or show name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does describe the return composition (Mozaika picks, vetted outside titles, hub URL) and flags that outside titles are 'text only', which is genuinely useful, but it says nothing about permissions, read-only status, rate limits, or what happens when no hub exists for the anchor.

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 followed by the return contents, with an illustrative example that earns its place. There is minor redundancy ('comparison hub' plus 'reading guide' plus 'hub URL from Mozaika Publications') that could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read lookup this covers the trigger and return shape adequately, and the absence of an output schema is partly compensated by the described return contents. Edge behavior (no hub found, empty results, locale fallback) is left unaddressed, which is a real gap given there are no annotations to fall back on.

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 documents both parameters and the baseline is 3. The description does add meaning by widening the anchor beyond the schema's 'title or show' to author and trope anchors, but it says nothing about how lang affects results, so the added value is modest.

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 ('Find') and resource (a comparison hub or reading guide) keyed to an anchor entity, so the agent knows this is a lookup that returns curated similar titles plus a hub URL. It does not name or distinguish itself from siblings like search_books or get_book, and 'comparison hub' is somewhat internal jargon, which keeps it short of a 5.

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 through the reader-question example ('a dark romance series to binge'), which gives a concrete trigger. However, there is no explicit when-not guidance and no alternative named, so an agent must infer when to prefer this over search_books or list_tropes.

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