Skip to main content
Glama

Preview ebook pages

preview_ebook
Read-onlyIdempotent

See up to 4 sheets of an ebook as images, rendered exactly as its PDF would be (sheet 1 is the cover when it has one). Use it to check a new cover, a crowded page or a layout change before exporting or publishing, and describe what you see to the user. Read-only: nothing is exported or counted.

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": {
      "projectId": "<projectId>"
    },
    "name": "preview_ebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNoWhich sheets to see, 1-based as in the PDF (1 is the cover when the ebook has one), up to 4. Default [1].
projectIdYesThe ebook (list_ebooks gives ids).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is largely pre-covered. The description still adds useful context beyond them: rendering fidelity to the PDF, and 'nothing is exported or counted', which speaks to quota/accounting side effects not visible in annotations. It omits image resolution, latency, and any paging behavior, so it is incremental rather than rich.

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 output format and scope, followed by usage and safety. The cover/1-based detail is stated here and again in the schema, a small redundancy, but there is no filler or hedging.

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

Completeness5/5

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

For a two-parameter, read-only preview tool with full schema coverage and no output schema, the description covers return format (images), fidelity, quantity limits, intended use, and side-effect freedom. Nothing an agent needs in order to call it correctly is missing.

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%, and the schema already documents the 1-based page numbering, the cover convention, the default [1], and the 1–4 cap. The description repeats the max-4 limit and the cover rule without adding syntax or edge-case guidance (e.g. out-of-range page indices), so the baseline 3 applies.

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 ('See up to 4 sheets of an ebook as images') and pins down the output format ('rendered exactly as its PDF would be'), which separates it from get_ebook metadata or export_ebook. It never names a sibling tool, so an agent must infer the boundary rather than read it, keeping this below 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete use cases — checking a new cover, a crowded page, or a layout change — and a timing cue ('before exporting or publishing') that implicitly routes the agent away from export_ebook/publish_lead_magnet. It also tells the agent what to do with the result ('describe what you see to the user'). No explicit when-not or named alternative, so 4 rather than 5.

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