Skip to main content
Glama

Pick photos for a photo book

start_photo_book
Read-onlyIdempotent

Use this when someone wants to make a printed photo book (Dutch: fotoboek) or photo album but has not shared any photos yet. Shows a card where they pick the photos, in order, right here. Nothing is ordered 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": "start_photo_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
languageNoTwo-letter code of the language the person writes in, such as nl or en.

Output Schema

NameRequiredDescriptionDefault
stepNo
titleNo
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the description's real contribution is the concrete behavior: a card appears for picking photos in order, and 'nothing is ordered or charged'. That clarifies the user-facing interaction and the no-side-effect boundary beyond the annotation flags.

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?

Three short sentences, front-loaded with the trigger condition and followed by the interaction and billing guarantee. No filler, though the parenthetical language note interrupts the flow slightly.

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?

With an output schema present, return values need not be explained, and the description covers trigger, UI behavior and cost safety. The main gap is the undocumented title parameter, which leaves the agent guessing about naming the book.

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

Parameters2/5

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

Schema coverage is only 50% (language is documented, title is not) and the description mentions neither parameter, so it adds no meaning about what title or language control. For a low-coverage schema, the description should compensate and does not.

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?

Names a specific action (start a photo book) and its scope (photo selection, not ordering), with a useful Dutch synonym 'fotoboek'. It does not explicitly separate itself from the sibling create_book, so an agent must infer which of the two actually builds the book.

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 a clear trigger condition: the person wants a printed book but 'has not shared any photos yet', which implies the alternative path once photos exist. It stops short of naming a specific alternative tool such as create_book for that later step.

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