Skip to main content
Glama

Mozaika Books Catalog

get_book

Get one Mozaika Publications work by author_slug and work_slug: catalog card, public chapter recap summaries, reading order hints, and canonical URL. Never returns full novel text.

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": {
      "author_slug": "<author_slug>",
      "work_slug": "<work_slug>"
    },
    "name": "get_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLocale code (default en).
work_slugYes
author_slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does useful work by enumerating the payload (catalog card, chapter recap summaries, reading order hints, canonical URL) and by explicitly negating a common expectation with "Never returns full novel text," which prevents an agent from calling it for plot text. It is silent on error behavior for unknown slugs, locale fallback effects, permissions, and payload size, which leaves meaningful gaps for a no-annotation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the identifier and resource before the payload list. The exclusion clause sits last as the natural caveat, and no wording is redundant with the tool name.

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 simple three-parameter read with no output schema, the description covers what the tool does and what it returns, plus the negative scope that matters most. Missing only slug-format and not-found behavior, which is a modest gap rather than a blocking one.

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 only 33%: lang is documented in the schema, but author_slug and work_slug are bare strings with no description. The description compensates partly by framing them as a composite key identifying one work, but it never explains slug format, where to obtain them, or case/sensitivity rules.

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?

A specific verb plus resource ("Get one Mozaika Publications work") with the exact lookup keys named, which is far more than a restatement of the name. It does not distinguish itself from the siblings books_like, list_tropes, or search_books, so an agent must infer that this is the single-item lookup rather than a discovery tool.

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?

The phrase "by author_slug and work_slug" implies you use this when you already know a specific work, which weakly suggests search_books or list_tropes are the paths for discovery. There is no explicit when-to-use or when-not-to-use statement, and no prerequisites or guidance about what to do when the slugs are unknown.

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