API Ninjas

solveSudoku

Read-only

Solves a Sudoku puzzle supplied in the request body. Requires the grid's box width and height. To create a new puzzle instead use /sudokugenerate.

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": {
      "width": "<width>",
      "height": "<height>",
      "body": "<body>"
    },
    "name": "solveSudoku"
  }
}

Input Schema

Name	Required	Description
`body`	Yes
`width`	Yes	Width of each box in the Sudoku grid. Must be between 2 and 4.
`height`	Yes	Height of each box in the Sudoku grid. Must be between 2 and 4.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The readOnlyHint=true annotation already tells the agent this is a non-destructive compute call, so the bar is lower. The description adds that the puzzle arrives in the request body and that box dimensions are mandatory, but says nothing about failure behavior on inconsistencies or about the shape of the result.

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

Conciseness5/5

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

Two short sentences with no filler, front-loading the core action and then the sibling routing. Every clause carries information.

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?

There is no output schema, so the description should ideally state what a successful solve returns and what happens to an unsolvable grid; it does neither. The body parameter's format is also left implicit. Adequate minimum viability for a simple 3-parameter 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 a moderate 67%: width and height are documented in the schema, and the description's phrase 'the grid's box width and height' usefully reinforces that these are box, not grid, dimensions. However the most complex parameter, body, is undocumented in both schema and description — its row/cell structure and the 0/null convention for blanks must be inferred.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 puzzle') and explicitly distinguishes itself from the sibling generateSudoku, which creates rather than solves puzzles. An agent can route between the two without opening either schema.

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

Usage Guidelines4/5

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

Gives a clear selection rule against the alternative ('To create a new puzzle instead use /sudokugenerate') and states the prerequisite that width/height are required. It stops short of full when/when-not framing (e.g., behavior on unsolvable or malformed grids), so 4 rather than 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All API Ninjas tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?