Skip to main content
Glama

Printablesmith

Math worksheet

make_math_worksheet
Read-onlyIdempotent

Make printable math worksheets with an answer key. Pick a skill (one of the site’s 60 ready skills, e.g. addition-within-10, addition-within-20, 2-digit-addition-without-regrouping, 2-digit-addition-with-regrouping, 3-digit-addition-with-regrouping, subtraction-within-10, times tables, fractions, telling time, money, place value, number bonds…), or build your own arithmetic sheet with operation and number ranges. Up to 20 sheets, each with different problems.

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_math_worksheet"
  }
}

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.
paperNoPaper size: letter (US Letter, the default; US and Canada) or a4 (everywhere else).
skillNoA ready skill (the math worksheet pages of the site). Leave out to use operation and ranges.
titleNoThe title printed at the top of the sheet, e.g. "Two-Digit Addition". Keep it short.
layoutNovertical (stacked) or horizontal (in a line).
sheetsNoHow many different sheets.
problemsNoProblems on each sheet.
operationNoOwn arithmetic: add, sub, mul, div, addsub (mixed + and −) or all (mixed).
answer_keyNoAnswer keys at the end (on by default).
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.
regroupingNoAddition and subtraction: any, none (no carrying or borrowing) or always.
remaindersNoDivision: allow remainders.
dyslexia_fontNoPrint in OpenDyslexic, a typeface some readers with dyslexia find easier.
first_numbersNoThe range of the first number, [min, max], e.g. [10, 99] for two digits.
second_numbersNoThe range of the second number, [min, max]; for times tables [7, 7] gives only ×7.

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

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds meaningful generation behavior: up to 20 sheets, each with different problems, and an answer key appended. It does not say what artifact is returned or whether generation is expensive, though an output schema exists to cover the return shape.

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 opening sentence and the closing sheet-count sentence are tight and front-loaded. The long parenthetical enumerating thirteen of sixty skill slugs largely duplicates the enum already present in the schema and bloats the middle of the definition without adding selection power.

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?

For a 15-parameter, zero-required tool with full schema documentation and an output schema, the description covers what the tool produces, the two authoring paths, and the multi-sheet limit. The only real gap is precedence when a caller supplies both a skill and operation/range values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 100%, the baseline would be 3, but the description adds the non-obvious relationship the schema cannot express: skill and operation/ranges are alternative modes, not additive settings. The example skill names illustrate naming conventions beyond the raw enum list.

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 printable math worksheets with an answer key") and immediately names the two authoring modes: a ready skill or a custom arithmetic sheet with operation and ranges. The subject matter alone separates it cleanly from the spelling, tracing, bingo, and crossword siblings.

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 clear routing inside the tool: supply a skill, or leave skill out and use operation plus number ranges. It also points to find_printables as the way to discover decoration theme names. It stops short of stating when to prefer this over a sibling maker, but the domain is unambiguous.

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