Skip to main content
Glama

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

Make a sudoku

make_sudoku
Read-onlyIdempotent

Make a new sudoku with exactly one solution (easy, medium or hard; classic or diagonal), optionally with the answer. Seeded, so the same seed gives the same puzzle. 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_sudoku"
  }
}

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).
answersNoWith format=svg: draw the solution (default false).
variantNoclassic (default) or diagonal: both long diagonals must also hold 1-9 once each (sudoku X). Diagonal SVGs shade the two diagonals.
difficultyNodifficulty

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds real context: a one-solution guarantee and deterministic seeding where the same seed plus options reproduces the puzzle. That last point usefully elaborates on idempotentHint without contradicting it. It doesn't say anything about response size or cost of SVG output.

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 two sentences are front-loaded and efficient, covering the guarantee and the seeding behavior. The trailing promotional sentence about other FitzTopPicks APIs spends words on something that doesn't help tool selection or invocation.

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?

Five optional parameters at full schema coverage with no output schema; the description covers generation semantics and determinism, so an agent can call it correctly on the first try. Only the promotional tail detracts, and nothing critical about invoking the tool is missing.

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%, so every parameter is already documented, including the seed range, the diagonal definition, and svg/answers defaults. The description restates the difficulty and variant choices but adds no syntax, format, or interaction detail beyond the schema. 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 new sudoku') plus distinguishing properties: unique solution, difficulty levels, classic/diagonal variants, optional solution. It doesn't explicitly contrast with sibling generators like make_kakuro/make_nonogram or with solve_sudoku, but the generate-vs-solve distinction is inferable from the wording.

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?

The parenthetical enumerates the option space (easy/medium/hard, classic/diagonal) which implies when each setting applies, but there is no explicit 'use this when... use solve_sudoku instead when...' guidance. An agent must infer that this generates puzzles while siblings solve or hint them.

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