Skip to main content
Glama

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

Solve a sudoku

solve_sudoku
Read-onlyIdempotent

Solve a sudoku from its 81-character grid and say whether the solution is unique. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "grid": "<grid>"
    },
    "name": "solve_sudoku"
  }
}

Input Schema

NameRequiredDescriptionDefault
svgNoInclude SVG images of the puzzle and its solution (default false).
gridYesThe puzzle: 81 characters, 1-9 or 0/. for empty.

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 readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds one real behavioral fact beyond them: it reports whether the solution is unique. It does not say what happens for unsolvable or malformed grids, and it spends a sentence on an unrelated promotional link.

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 functional sentence is front-loaded and tight, but the second sentence is pure API promotion with zero bearing on invoking this tool, which dilutes an otherwise compact definition.

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 explain the return shape; it hints at a solution plus a uniqueness flag but omits the unsolvable case and whether SVG output changes the response. Adequate for a simple, fully-annotated read tool, but not complete.

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%, including the 81-character length constraint and the 1-9/0/. convention, so the baseline is 3. The description merely restates '81-character grid' and adds nothing about the svg parameter's effect on the response.

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: solves a sudoku from an 81-character grid and reports solution uniqueness. That distinguishes it from a pure puzzle generator, but it never names make_sudoku or sudoku_hint, so an agent must infer the boundary itself.

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. With siblings like make_sudoku (generation) and sudoku_hint (partial help) present, the description gives no signal about which to select for a given task.

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