Skip to main content
Glama

Generate a maze

generate_maze

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 observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses the invariants — exactly one solution per maze and seed-to-maze determinism — but says nothing about what the response actually contains for each format (raw SVG markup, a file, ASCII in a text block) or about any size limits on returned payloads.

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 with the core purpose front-loaded and the guarantees trailing. The shape enumeration duplicates the `shape` enum and could be trimmed, but nothing is padded or vague.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description never explains the return value beyond naming the three serializations, which matters for an agent that must handle an SVG blob versus structured JSON. For an eight-parameter generative tool the coverage is decent but leaves a real gap at the response end.

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 parameters are already fully documented, including size guidance and the format trade-offs. The description repeats the shape list and the country hint that already exist in the enum and field descriptions, adding little new meaning beyond confirming the single-solution guarantee.

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 opening sentence gives a specific verb and resource ("Generate a printable maze") plus the three output encodings, so the tool's function is unambiguous. It does not differentiate itself from the sibling find_printable_mazes, leaving the agent to infer that this one creates mazes rather than searching a catalog.

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 hints are parameter-scoped ("pass `country`", "set show_solution for an answer key") rather than situational. There is no explicit when-to-use versus when-not guidance, and no routing to find_printable_mazes or list_countries, so an agent must infer the choice from names.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.