Skip to main content
Glama

Find ready-made printable mazes

find_printable_mazes

Search 2,000+ free printable mazes by theme or topic and get links to print-ready pages with answer keys; leave the query empty to list themes.

Instructions

Search 2,000+ free printable mazes on MazeDIY (animals, dinosaurs, holidays, vehicles, food, US states and more). Each result links to a page with a print-ready maze and its answer key. Leave the query empty to list themes.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoWhat the maze should look like, e.g. "dinosaur", "christmas tree", "Texas".
themeNoLimit to one theme, e.g. "Animal Mazes".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the return shape (each result links to a page with a print-ready maze and answer key), which is useful. It says nothing about whether results are paginated, rate-limited, or how the 2,000+ corpus is filtered or ordered.

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 sentences, front-loaded with the corpus size and scope, then the result format, then the empty-query tip. The category list is slightly long but earns its place by showing coverage.

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 supplies the missing return-value context in one sentence. For a simple three-parameter, zero-required search tool, the main residual gap is the absence of any differentiation from the maze-generating sibling.

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 67%, with query and limit documented in the schema while theme is not. The description partially compensates by enumerating sample themes (animals, dinosaurs, holidays, vehicles, food, US states) and by explaining the empty-query fallback, but it never explains limit or how theme interacts with query.

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 states a specific verb and resource (search 2,000+ free printable mazes on MazeDIY) and scopes the corpus with concrete categories. An agent can tell it retrieves ready-made mazes as opposed to generating one, though it never explicitly contrasts with the generate_maze sibling.

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?

It provides one concrete usage rule — 'Leave the query empty to list themes' — which tells the agent how to browse rather than search. There is no guidance on when to prefer this over generating a maze, and no mention of how theme differs from query in selection terms.

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

Deploy Server

Other Tools