Skip to main content
Glama

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

Make a kakuro

make_kakuro
Read-onlyIdempotent

Make a kakuro (cross sums) puzzle 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_kakuro"
  }
}

Input Schema

NameRequiredDescriptionDefault
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).
sizeNosize
answersNoWith format=svg: draw the solution (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the generated puzzle has exactly one solution — but says nothing about output shape or cost, which matters with no output schema.

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?

The first sentence is tight and front-loaded with the key constraint. The second sentence is a promotional URL that does nothing for tool selection and is pure 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 no output schema, the description should hint at what comes back (puzzle grid, seed, optional SVG/solution), which it does not. It does, however, convey purpose and the uniqueness guarantee, which are the main decision factors.

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 100% and the parameter descriptions already explain seed determinism, svg, and answers thoroughly. The description adds no parameter meaning beyond the schema, so 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?

States a specific verb and resource ("Make a kakuro (cross sums) puzzle") plus a distinguishing quality guarantee ("with exactly one solution"). It is clearly separable from make_sudoku/make_maze/make_nonogram by resource name, though it never explicitly contrasts with them.

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?

No when-to-use or when-not-to-use guidance, and no routing among the several puzzle-generator siblings. The only implied usage is the obvious 'call this to get a kakuro'.

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