Printablesmith

Maze

make_maze

Read-onlyIdempotent

Make printable mazes with solutions, from very easy (xs, preschool) to very hard (xl). Up to 50 different mazes, 1, 2 or 4 a page. Children can also solve them on a screen.

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_maze"
  }
}

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.
`size`	No	How big and hard: xs (preschool), s, m, l or xl (very hard).
`mazes`	No	How many different mazes.
`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. "Maze Fun". Keep it short.
`per_page`	No	Mazes on each page.
`solutions`	No	Solutions at the end.
`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.
`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.
`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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds real behavioral context beyond that: output is a printable sheet, mazes can carry solutions at the end, layout can hold 1/2/4 per page, and the result is also screen-solvable. It does not mention pagination or limits beyond the schema's own cap.

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, purpose front-loaded, then capabilities, then the screen note. Nothing is padded, though the closing sentence about children solving on a screen is only marginally useful for invocation decisions.

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 10 optional parameters, an output schema, and rich annotations, the description only needs to frame the tool rather than document each knob, and it does so adequately. A brief note on what the returned artifact looks like or on how seed interacts with regeneration would have closed the remaining gap, though the seed parameter description already covers that.

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% and each parameter already carries a detailed description (seed reuse semantics, size difficulty mapping, decoration themes, large_print rationale), so the schema does the heavy lifting. The description reinforces size difficulty and per-page counts but adds no syntax or default information the schema lacks, making the baseline 3 appropriate.

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 gives a specific verb and resource ('Make printable mazes with solutions') plus a difficulty range from xs/preschool to xl, which is enough to tell it apart from make_sudoku or make_word_search by resource alone. It stops short of explicitly naming a sibling or stating the boundary case (e.g., mazes vs. other puzzle printables).

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 is only implied: 'Children can also solve them on a screen' hints at a digital use case, and the size range hints at audience selection, but there is no explicit when-to-use or when-not-to-use guidance versus the many other make_* printable tools. An agent must infer that this is the right tool whenever the artifact is a maze.

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?