Skip to main content
Glama

Coloring books

books
Destructive

List, get, create, update, copy, or delete the signed-in user's coloring books. A book holds up to 100 pages. Create accepts up to 50 coloring pages plus an optional front cover and back cover. create stores pageLayout; layout is an alias. create with startGeneration requires confirmToken from a plan quote. Pass the quote locked object. status is the stored book status. activity is generating while any page is generating. Image generation spends the website token balance. Purchases happen at /pricing; this tool never takes payment.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds materially: capacity limits (100 pages per book, 50 per create), the fact that image generation spends the site token balance, and the confirmToken precondition. It stops short of stating what delete or copy actually do (cascade, duplication semantics, reversibility) and the `status`/`activity` sentences are asserted without enough context to be actionable.

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

Conciseness3/5

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

The operation list is correctly front-loaded, but the body degenerates into terse fragments ('Pass the quote locked object.', 'status is the stored book status.', 'activity is generating while any page is generating.') that read ambiguously and restate schema facts. Several sentences would need rewriting to be useful rather than merely short.

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 six-operation tool with a large discriminated-union schema and no output schema, the description covers creation, quotas, cost, and the confirmToken flow well. It leaves `list`, `get`, `copy`, and `delete` almost entirely undescribed, and the unexplained `activity` field implies return values that are never characterized.

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 effectively 100%, and the schema itself already documents the layout/pageLayout alias and the confirmToken quote-matching rule, so the description mostly echoes structured data. The genuinely additive details are the 100-page book cap versus the 50-page create cap, which constrains how `pages` should be sized.

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?

The opening sentence names the resource (the signed-in user's coloring books) and enumerates the six operations in one pass, so an agent knows this is a multi-op CRUD tool. It does not distinguish itself from the sibling `pages` tool or explain the boundary with `generate`, despite create accepting coloring pages.

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?

There is real conditional guidance for the trickiest path: create with startGeneration requires a confirmToken from a plan quote. It also rules out payment handling by directing to /pricing. However, there is no when-to-use-this-vs-alternatives guidance against the listed siblings (`pages`, `generate`, `export`), which is where an agent is most likely to misroute.

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