Skip to main content
Glama
Sign In

Printablesmith

by com.printablesmith
OverviewDiscussionsAdmin

Sudoku

make_sudoku
Read-onlyIdempotent

Make printable sudoku puzzles with solutions: 4 × 4 for children, 6 × 6, or classic 9 × 9, easy to hard, and large print for older adults. Up to 60 puzzles, up to 6 a page. They can also be played on a screen.

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
seedNoWhich random version to make. Leave out for a fresh one; pass the seed from an earlier result to keep that version while changing other settings.
sizeNo4 (4 × 4, children), 6 or 9 (classic).
paperNoPaper size: letter (US Letter, the default; US and Canada) or a4 (everywhere else).
titleNoThe title printed at the top of the sheet, e.g. "Sudoku". Keep it short.
puzzlesNoHow many different puzzles.
per_pageNoPuzzles on each page (2 at most in large print).
solutionsNoSolutions at the end.
decorationNoA themed border with matching pictures, drawn around the sheet: "line" for a plain border, "none" for nothing, or a theme such as halloween, christmas, thanksgiving, spring, dinosaurs, space, ocean, animals, birthday, back-to-school (95 themes; find_printables shows a theme’s name). Leave out for no border.
difficultyNoHow hard: easy, medium or hard.
for_seniorsNoStart from the older adults’ sudoku page, in large print.
large_printNoLarge print for older eyes or low vision: bigger, bolder letters and roomier layouts (sizes are capped to fit). For young children, use large.
dyslexia_fontNoPrint in OpenDyslexic, a typeface some readers with dyslexia find easier.

Output Schema

NameRequiredDescriptionDefault
urlYesThe sheet on printablesmith.com, every setting filled in: open it to adjust, download the PDF or print
seedNoThe seed that rebuilds this exact sheet
makerYesWhich maker drew it, e.g. wordSearch
notesYesThings worth knowing about this sheet
titleYesThe sheet title
playUrlNoWhere a child can solve it on a screen (word search, crossword, maze, sudoku)
summaryYesWhat the sheet is
settingsYesThe address settings, as the maker reads them

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 real behavioral constraints beyond that: a 60-puzzle cap, at most 6 per page, and the cross-cutting rule that large print caps sizes and allows at most 2 puzzles per page — non-obvious interaction rules the schema states only in fragments.

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

Conciseness4/5

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

Two compact sentences, front-loaded with the core action and variant space, with no filler. Minor deduction for the trailing 'They can also be played on a screen' and the unclear 'use large' clause, both of which cost a bit of precision without adding much decisiveness.

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 12 all-optional parameters and an output schema present, the description need not explain return values, and the schema documents every parameter. What remains thin is discovery-oriented context — how themes are found, or when to prefer a different maker — though nothing essential for calling the tool correctly 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 description coverage is 100%, so nearly all parameter meaning is already carried by the schema, making 3 the baseline. The description does contribute the large-print/per_page interaction and the seniors-vs-children framing, but it also introduces ambiguity with 'For young children, use large', which reads as advice about the size parameter without naming it.

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?

The description uses a specific verb+resource ('Make printable sudoku puzzles') and enumerates the variant space (4×4, 6×6, 9×9, easy to hard, large print), which clearly separates it from non-puzzle siblings like make_chart or make_certificate. It never explicitly names a sibling alternative (e.g. make_crossword or find_printables), so it stops short of a 5.

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 through audience cues ('4 × 4 for children', 'large print for older adults', 'can also be played on a screen'). There is no explicit when-to-use / when-not-to-use guidance and no routing to related tools such as find_printables for themes or describe_maker for option discovery.

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

All Printablesmith toolsInspect
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