Skip to main content
Glama

Generate a maze

generate_maze

Generate printable single-solution mazes in shapes such as rectangle, circle, heart, star, or country outlines as SVG, ASCII, or JSON. Reuse a seed to reproduce the same maze or show the answer key.

Instructions

Generate a printable maze as SVG, ASCII text or JSON. Shapes: rectangle, circle, heart, star, diamond, triangle, hexagon, or the outline of any country (pass country). Every maze has exactly one solution; set show_solution for an answer key. The same seed always gives the same maze.

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

Input Schema

NameRequiredDescriptionDefault
seedNoReuse a seed to regenerate the same maze.
sizeNoCells along the longer side. 10-15 suits young children, 20-30 older kids, 40+ adults.
shapeNoMaze outline. Use "country" together with the `country` field.rectangle
widthNoRectangle only: cells across. Overrides size.
formatNosvg for printing, ascii for chat (best at size 25 or less), json for programs.svg
heightNoRectangle only: cells down. Overrides size.
countryNoCountry name, ISO code or alias, e.g. "Italy", "JP", "USA". Implies shape "country".
show_solutionNoDraw the solution path (answer key).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does real work: it guarantees exactly one solution per maze, documents seed-based determinism, and flags show_solution as an answer key. It does not state that generation is side-effect free or describe the shape/size of the returned payload, leaving a modest gap.

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?

Four short sentences, front-loaded with the core capability, then shapes, then behavioral guarantees. The shape enumeration duplicates the schema enum and is the one block of text that does not fully earn its place, but overall it is tight.

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?

For an 8-parameter, zero-required, fully documented generation tool with no output schema, the description covers formats, shapes, determinism and the solution flag adequately. It could say more about what is actually returned (an SVG string vs. ASCII block) since no output schema exists to cover 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%, so every one of the 8 parameters is already documented, establishing a baseline of 3. The description largely restates enum values and the seed-determinism note already present in the schema, adding only the implicit 'country implies shape' hint, which is also in the schema.

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 opens with a specific verb+resource ('Generate a printable maze') and enumerates the output formats and shape families, so an agent knows exactly what the tool produces. It does not distinguish itself from the sibling find_printable_mazes or explain that list_countries feeds the `country` option, so it stops short of full sibling differentiation.

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 implied by the artifact type (printable maze, puzzle/worksheet generation), and the country branch hints at a workflow with list_countries, but there is no explicit when-to-use/when-not guidance and no statement of when to prefer this over find_printable_mazes. Format selection advice ('svg for printing, ascii for chat') lives only in the schema, not in the description.

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