Skip to main content
Glama

Book plan and order form

create_book_plan
Read-onlyIdempotent

Makes the plan for the book and returns the link to the order form on the website with the occasion and story line filled in. The parent then enters the child's name and photo there.

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": {
      "language": "<language>",
      "occasion": "<occasion>"
    },
    "name": "create_book_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
storyNoStory line id from list_occasions; empty for the best one
styleNoStyle id from show_styles, if the user chose one
languageYesTwo-letter code of the language the user writes in, e.g. 'en', 'nl', 'de'
occasionYesOccasion id from list_occasions, e.g. 'verjaardag' or 'kerst'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, idempotent, closed-world, so the safety bar is met. The description adds the non-obvious behavior that no order is placed here: it returns an external order-form link pre-filled with occasion and storyline, and a human completes name and photo. It does not say whether a plan is persisted or how long a link lives.

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 tight sentences, front-loaded with the action and followed by the handoff detail; nothing is filler. Could be slightly sharper by naming list_occasions/show_styles as the id sources rather than leaving that to the schema.

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 no output schema, the description correctly compensates by stating that the return is a URL to the order form. Combined with 100% parameter coverage and read-only annotations, an agent has enough to call it correctly; only plan persistence/link lifetime is unaddressed.

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%, so all four parameters (including 'story', 'style', 'language', 'occasion') are already documented with source lists. The description adds only the aggregate point that occasion and story get 'filled in' on the resulting form, which is a small semantic gain over the schema — baseline 3.

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 artifact ("makes the plan for the book") and, crucially, the actual return value: a link to the order form. That return-value statement is what distinguishes it from list_occasions/show_styles, which merely supply ids, though the description never names those siblings explicitly.

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?

Implies the workflow clearly: you supply an occasion/story id drawn from list_occasions and get a pre-filled order link, after which the parent finishes the form. It does not spell out an explicit 'use this when / not when' rule or name alternatives, but the context is unambiguous.

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