Skip to main content
Glama

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

Make a nonogram

make_nonogram
Read-onlyIdempotent

Make a nonogram (picture logic puzzle, 5x5 to 25x25) with exactly one solution, solvable by line logic. 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_nonogram"
  }
}

Input Schema

NameRequiredDescriptionDefault
hNoHeight in squares, 5-25 (default: the width).
wNoWidth in squares, 5-25 (default 10).
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).
densityNoHow much of the picture is filled.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful guarantees beyond that: the puzzle has exactly one solution and is solvable by pure line logic, which constrains what the caller will receive and is not expressed anywhere in the schema or annotations.

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 sentence is tight, front-loaded, and earns its place. The trailing sentence, however, is a promotional URL block ("More APIs from FitzTopPicks...") with tracking parameters that gives the agent no information about invoking this 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?

Six optional parameters with zero required, fully described in the schema, plus annotations covering the safety profile and a description covering the puzzle-quality guarantees. What remains thin is the response shape (no output schema and only passing mention that the response reports the seed used), which is a modest gap rather than a blocking one.

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%, so every parameter (h, w, svg, seed, answers, density) is already documented with ranges, defaults, and determinism semantics. The description restates only the size range (5x5 to 25x25) and adds no meaning the schema lacks, so the baseline 3 applies.

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 ("Make a nonogram") and immediately qualifies the artifact: picture logic puzzle, 5x5 to 25x25, exactly one solution, solvable by line logic. That distinguishes it cleanly from sibling generators such as make_sudoku, make_kakuro, and make_maze without needing their schemas.

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?

Usage is only implied by the tool's nature as a puzzle generator; there is no explicit when-to-use or when-not-to-use statement and no routing to sibling puzzle tools. Given the sibling set is a broad catalog of unrelated utilities, the omission is tolerable, but the description does no active work here.

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