Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Make a maze

make_maze
Read-onlyIdempotent

Make a perfect maze (one path from entrance to exit) up to 60x60, optionally with the solution path. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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

NameRequiredDescriptionDefault
hNoHeight in squares, 2–60 (default: the width).
wNoWidth in squares, 2–60 (default 15).
svgNoInclude SVG images of the puzzle and its solution in the JSON (default true).
seedNoWhole number 0–4294967295. The same seed and options always give the same puzzle; leave it out for a random one (the response tells you the seed it used).
answersNoWith format=svg: draw the solution (default false).
markersNoDraw START and FINISH labels in the SVG (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description contributes the definition of a 'perfect maze' and the 60x60 ceiling, which is useful domain context. It omits that output is JSON containing SVG images and says nothing about determinism beyond what the seed parameter already documents.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is tight and front-loaded with the essential capability and constraint. The second sentence is pure promotional filler about other APIs, which earns no place in a tool definition and dilutes the signal.

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?

For a zero-required-parameter generator with a fully documented schema and safety annotations, most of what an agent needs is present. However, with no output schema, the description never states the response shape — that JSON with optional SVG images is returned — leaving a gap the agent must guess.

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% with well-documented defaults, ranges and seed semantics, so the schema carries the parameter burden. The description only echoes the 60x60 limit and the optional solution path, both already stated in the schema. Baseline 3 is 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?

States a specific verb and resource ('Make a perfect maze') and adds a precise domain qualifier — 'one path from entrance to exit' — plus a size ceiling of 60x60. An agent can immediately tell this is a maze generator distinct from make_sudoku or make_nonogram, though the description does not name any sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no routing to alternatives. The only usage signal is the incidental mention of an optional solution path, which is really a parameter hint rather than selection criteria.

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.

Resources