Skip to main content
Glama

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

Next sudoku step, explained

sudoku_hint
Read-onlyIdempotent

What is the next logical move in this sudoku? The simplest technique that makes progress (hidden single, pointing pair...), named and explained, without giving the whole answer. 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": "sudoku_hint"
  }
}

Input Schema

NameRequiredDescriptionDefault
gridYesThe grid as the player has it now: 81 characters, 1-9 or 0/. for empty.
originalNoThe starting puzzle (81 characters). With it, entries that differ from the solution are returned as mistakes.
candidatesNoInclude the pencil marks (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint false, openWorldHint false), so the description only needs to add behavioral color — and it does, disclosing that the result is a named, explained technique chosen by simplicity and deliberately partial. It does not say what happens with a filled or inconsistent grid, which is a minor remaining gap given the annotations already establish the read-only profile.

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 tight and front-loaded with the core question and the key constraint. The trailing 'More APIs from FitzTopPicks' link with UTM tracking is promotional filler that does not help an agent select or invoke the tool and dilutes an otherwise clean definition.

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?

With no output schema, the description carries the burden of explaining the return value, and it does so qualitatively (a named, explained technique). Combined with 100% schema coverage for the three parameters and annotations covering safety, an agent has nearly everything needed; only edge-case behavior for malformed or completed grids is unstated.

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%, and each parameter (grid, original, candidates) is documented in the schema with format and effect, so the schema carries the load. The description adds no parameter-level meaning beyond what is already structured — baseline 3.

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?

The description states a specific operation on a specific resource — return the next logical sudoku move — and immediately narrows it: 'The simplest technique that makes progress (hidden single, pointing pair...), named and explained, without giving the whole answer.' The clause 'without giving the whole answer' implicitly separates it from a full solver, so an agent can distinguish it from solve_sudoku without reading 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?

The framing question and the 'without giving the whole answer' constraint make the use case clear: call this when the user wants a nudge rather than the solution. It does not name an explicit alternative or state exclusions in so many words, so the routing is strong but inferred rather than spelled out.

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