Printablesmith

Scavenger hunt

make_scavenger_hunt

Read-onlyIdempotent

Make a printable scavenger hunt checklist with a picture for each thing to find (indoor, outdoor, nature, classroom, party or your own list). Up to 30 items of up to 40 characters.

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": "make_scavenger_hunt"
  }
}

Input Schema

Name	Required	Description
`page`	No	A ready hunt to start from (its own list), or maker for your own.
`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.
`show`	No	pictures (a picture for each, best for young children) or words only.
`items`	No	The things to find.
`paper`	No	Paper size: letter (US Letter, the default; US and Canada) or a4 (everywhere else).
`title`	No	The title printed at the top of the sheet, e.g. "Backyard Scavenger Hunt". Keep it short.
`labels`	No	Print the names under the pictures.
`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.
`dyslexia_font`	No	Print in OpenDyslexic, a typeface some readers with dyslexia find easier.

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

A3.5/5.0

Behavior3/5

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

Annotations already establish this as a safe, idempotent, non-destructive read that produces a printable artifact, so the description's main added value is the hard constraints of 30 items at 40 characters each. It says nothing about output format, how themes are resolved, or how seed reproducibility interacts with other settings, leaving meaningful behavioral context undocumented.

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?

The definition is two tightly packed sentences with the core purpose front-loaded and zero filler. The parenthetical theme list and trailing size limits are useful but slightly crammed together, costing a little readability.

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 nine optional parameters, full schema coverage, rich annotations, and an output schema, the description supplies enough to call the tool correctly. Remaining gaps are around theme discovery and parameter interplay, which are nice-to-have rather than blocking.

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 heavy lifting is already done and a 3 is the baseline. The description's item and character limits restate what the schema enforces (maxItems 30, maxLength 40) rather than adding new meaning, and it does not clarify interactions among page, items, seed, or decoration.

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 description names a specific verb and resource ('Make a printable scavenger hunt checklist') and states the core output (a picture per item). It distinguishes itself from siblings like make_bingo_cards or make_word_search by resource alone, but never explicitly routes the agent away from those alternatives.

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?

Usage context is implied through the parenthetical theme list ('indoor, outdoor, nature, classroom, party or your own list'), which suggests when this tool fits. There is no explicit when-not guidance, no mention of prerequisites, and no reference to find_printables or describe_maker for discovering themes.

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?