Skip to main content
Glama

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

Make a math cage puzzle

make_math_cages
Read-onlyIdempotent

Make a math cage puzzle (Latin square with arithmetic cages, 4x4 to 9x9) with exactly one solution. 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_math_cages"
  }
}

Input Schema

NameRequiredDescriptionDefault
opsNoOperations to use.
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).
sizeNoGrid size, 4-9 (default 6).
answersNoWith format=svg: draw the solution (default false).

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 fully covered. The description adds one genuinely useful behavioral promise beyond that: the generated puzzle has exactly one solution. It says nothing about response shape, how the puzzle and solution are returned, or seeding behavior (left to the schema), and the trailing marketing URL is pure noise.

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 core sentence is well front-loaded and dense with useful facts, but it is followed by a promotional line ('More APIs from FitzTopPicks: ...') that does not help an agent select or invoke the tool. Roughly half the text is waste.

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?

With five optional parameters, no required inputs, and no output schema, the description covers the essential concept and the uniqueness guarantee. However, it omits what the response actually contains (JSON with puzzle, solution, and the seed used), which matters for a tool with no output schema, and the promotional line displaces space that could have held that detail.

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 parameter (ops, svg, seed, size, answers) is already documented in the input schema. The description only echoes the 4x4–9x9 size range and adds no meaning about ops choices, SVG output, or answer drawing beyond what the schema states. Baseline 3 applies.

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?

Names a specific verb and resource ('Make a math cage puzzle') and defines it concretely as a 'Latin square with arithmetic cages, 4x4 to 9x9' with a unique solution, which lets an agent distinguish it from sibling generators like make_sudoku, make_kakuro, make_maze, or make_nonogram without opening the schema. It stops short of explicitly contrasting with those siblings, but the domain definition does the disambiguating work.

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 and no alternative tools are named. An agent must infer from the puzzle type alone that this is the cage/Latin-square generator rather than the sudoku or kakuro one. Only the 'exactly one solution' guarantee hints at a selection criterion.

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