Printablesmith

Activity pack

make_activity_pack

Read-onlyIdempotent

Make a whole activity pack from one word list, in one PDF: word search, word scramble, crossword, tracing, spelling, a spelling test, bingo, a maze and sudoku, with answer keys at the back. The fastest way to a themed set (a holiday, a unit, a party). spelling_week makes a Monday-to-Friday spelling set instead.

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": {
      "words": "<words>"
    },
    "name": "make_activity_pack"
  }
}

Input Schema

Name	Required	Description
`seed`	No	Which random version to make. Leave out for a fresh one; pass the seed from an earlier result to keep that version while changing other settings.
`large`	No	Bigger, bolder letters on every sheet for young children and beginning readers (for older eyes, use large_print).
`paper`	No	Paper size: letter (US Letter, the default; US and Canada) or a4 (everywhere else).
`title`	No	The pack’s title, printed on every sheet (up to 50 characters).
`words`	Yes	The words (up to 40). Give a clue after a dash for the crossword ("owl - A bird that hoots at night"); words without one get the site’s checked clue where it has one.
`sheets`	No	Which sheets (the default: word search, word scramble, crossword, tracing and bingo).
`decoration`	No	A themed border with matching pictures, drawn around the sheet: "line" for a plain border, "none" for nothing, or a theme such as halloween, christmas, thanksgiving, spring, dinosaurs, space, ocean, animals, birthday, back-to-school (95 themes; find_printables shows a theme’s name). Leave out for no border.
`answer_keys`	No	Answer keys at the back.
`bingo_cards`	No	How many bingo cards.
`large_print`	No	Large print for older eyes or low vision: bigger, bolder letters and roomier layouts (sizes are capped to fit). For young children, use large.
`letter_case`	No	upper or lower case letters on the puzzles.
`dyslexia_font`	No	Print in OpenDyslexic, a typeface some readers with dyslexia find easier.
`spelling_week`	No	A spelling week instead: five sheets, Monday to Friday, ending with the test.
`word_search_difficulty`	No	The word search’s difficulty: easy, medium or hard.

Output Schema

Name	Required	Description
`url`	Yes	The sheet on printablesmith.com, every setting filled in: open it to adjust, download the PDF or print
`seed`	No	The seed that rebuilds this exact sheet
`maker`	Yes	Which maker drew it, e.g. wordSearch
`notes`	Yes	Things worth knowing about this sheet
`title`	Yes	The sheet title
`playUrl`	No	Where a child can solve it on a screen (word search, crossword, maze, sudoku)
`summary`	Yes	What the sheet is
`settings`	Yes	The address settings, as the maker reads them

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond that: everything is combined into a single PDF and answer keys land at the back. It says nothing about generation time or whether a repeat call re-renders identically, but the seed parameter in the schema covers reproducibility.

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?

Two sentences, front-loaded with the capability and the output artifact, then the use case and the nearest alternative. Dense but every clause carries information; no filler.

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 14 parameters, full schema coverage, an output schema and annotations, the description needs only to frame the operation and it does so well. The remaining gap is the ambiguous spelling_week reference, which reads like a tool name rather than a flag, and no word on how this relates to the single-sheet makers.

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 100%, so the structured fields already explain every parameter, including defaults, enum values, the "word - clue" syntax and the seed reuse workflow. The description repeats the sheet list and the spelling_week concept without adding format or constraint detail, so it sits at the baseline.

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?

States a specific verb and resource ("Make a whole activity pack from one word list") and enumerates the deliverables: word search, scramble, crossword, tracing, spelling, test, bingo, maze, sudoku, with answer keys. The output format (one PDF) is named, so an agent can tell this apart from the single-activity siblings like make_word_search without opening a schema.

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 use context — "The fastest way to a themed set (a holiday, a unit, a party)" — which tells the agent when the bundle is preferable to assembling individual sheets. It omits explicit guidance on choosing this over the individual maker tools, and the closing sentence about spelling_week blurs whether that is a sibling tool or the parameter of the same name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Printablesmith tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?