Skip to main content
Glama

Lay out a printed book

layout_book
Destructive

Lays out supplied stories, memoirs, letters or recipes as a draft 8.5-inch square book with a page-by-page preview. An existing book ID updates only the supplied fields. The result includes a private editor link for text changes and picture uploads. No images are generated. Nothing is printed or charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "layout_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNopicture = one picture and short text per spread (children's stories); text = flowing chapters (memoirs, recipes, letters)
titleNoBook title
authorNoAuthor name as it should appear on the cover, e.g. "Grandma Rosa"
imagesNoPictures from the conversation, in the order referenced by sections
book_idNoId of a book made earlier, to update it
countryNoISO country code the book will ship to, if known, to show the right price
languageNoLanguage the book is written in (sets the printed words like "The End"). Defaults to the conversation language.
sectionsNoThe book content in order
subtitleNo
full_textNoAlternative to sections: the whole text; it is split at blank lines
dedicationNoDedication page text, e.g. "For Lucía, love Mum"
cover_imageNoIndex into `images` for the front cover; defaults to the first picture

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare mutability, open-world behavior, non-idempotency, and destructive potential. The description adds useful behavioral context: it produces a draft with a private editor link, generates no images, and neither prints nor charges. It does not elaborate on overwrite risks beyond saying updates affect only supplied fields, but that is a meaningful addition.

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?

The description is four tight sentences, front-loaded with what the tool does and immediately followed by update behavior, output form, and the key non-actions. Every sentence carries useful information without repetition.

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 12-parameter, open-world, non-read-only tool with no output schema, the description covers the essential outcome and limits: draft layout, preview, editor link, update behavior, no image generation, and no print or charge. Some return/persistence detail is only implied by the editor link, but the core completeness is strong.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already high at 92%, so the schema does most of the parameter documentation. The description still adds semantics beyond the schema by clarifying that an existing book ID updates only supplied fields and that images are supplied rather than generated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: lays out supplied stories, memoirs, letters or recipes as a draft 8.5-inch square book with a page-by-page preview. It also distinguishes the outcome from the create_print_order sibling by explicitly saying nothing is printed or charged.

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?

It gives clear usage context: this is for creating a draft layout and can update an existing book ID using only supplied fields. It does not explicitly name create_print_order or list_formats_and_prices as alternatives, so the when-to-use guidance is clear but lacks full sibling routing.

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