Printablesmith

Chart for home or class

make_chart

Read-onlyIdempotent

Make a printable chart for children and families: chore chart, reward (sticker) chart, potty training chart, behavior chart, visual schedule, first-then board, morning or bedtime routine chart, or habit tracker. Steps and chores get matching pictures automatically. Give names to print one chart per child (chore, reward and behavior charts; in the chat only).

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": {
      "kind": "<kind>"
    },
    "name": "make_chart"
  }
}

Input Schema

Name	Required	Description
`ink`	No	The ink color.
`days`	No	Chore and behavior charts: week (7 days) or school (5).
`goal`	No	Reward and behavior charts: the goal, e.g. "Use the potty" or "Kind hands".
`kind`	Yes	Which chart.
`seed`	No	Which 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.
`year`	No	Habit tracker: the year.
`items`	No	The chores (up to 12), schedule or routine steps (up to 12), behavior periods (up to 8, e.g. "Morning"), or habits (up to 15). Reward charts take a goal instead.
`month`	No	Habit tracker: the month to start, 1 to 12.
`names`	No	Optional names, one chart each (first names are enough). Shown and printed in the chat only: like the site, the link never carries names, so a person opening the link types them on the page.
`paper`	No	Paper size: letter (US Letter, the default; US and Canada) or a4 (everywhere else).
`title`	No	The title printed at the top of the sheet, e.g. "My Chores". Keep it short.
`layout`	No	Visual schedule only: strip, list, first_then or cards (for a first-then board, use kind first_then).
`reward`	No	Reward chart: what the child earns, e.g. "A trip to the park". Chore and behavior charts: any text turns on a reward line.
`spaces`	No	Reward chart: how many spaces to fill.
`pictures`	No	Chore chart and schedules: a picture for each item (on by default).
`decoration`	No	A 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.
`week_starts`	No	The first day of the week.
`goal_picture`	No	Reward chart: the goal’s picture.
`dyslexia_font`	No	Print in OpenDyslexic, a typeface some readers with dyslexia find easier.

Output Schema

Name	Required	Description
`url`	Yes	The sheet on printablesmith.com, every setting filled in: open it to adjust, download the PDF or print
`seed`	No	The seed that rebuilds this exact sheet
`maker`	Yes	Which maker drew it, e.g. wordSearch
`notes`	Yes	Things worth knowing about this sheet
`title`	Yes	The sheet title
`playUrl`	No	Where a child can solve it on a screen (word search, crossword, maze, sudoku)
`summary`	Yes	What the sheet is
`settings`	Yes	The address settings, as the maker reads them

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is covered. The description adds behavior beyond that: pictures are matched to chores/steps automatically, and names are 'shown and printed in the chat only' because 'the link never carries names', which is a non-obvious disclosure about the output artifact and privacy.

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 sentences, purpose front-loaded, no filler. The second sentence is slightly tangled with its parenthetical, but every clause carries actionable information about names and per-child duplication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 19-parameter generator with full schema coverage and an output schema, the description supplies what structure cannot: what the tool produces (a printable chart plus a link), the variant list, the automatic picture matching, and the names-only-in-chat caveat. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100% with 19 well-described parameters, so the baseline is 3. The description adds a cross-parameter constraint the schema does not state — that `names` only expands into multiple charts for chore, reward and behavior kinds — which prevents a misuse the schema alone would permit.

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 verb and artifact ('Make a printable chart') and then enumerates the nine concrete variants: chore, reward/sticker, potty training, behavior, visual schedule, first-then board, morning/bedtime routine, and habit tracker. That enumeration maps directly onto the `kind` enum and clearly separates it from siblings like make_bingo_cards or make_certificate.

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?

The chart-type list implies when the tool is the right choice, and 'Give names to print one chart per child (chore, reward and behavior charts)' gives a real usage rule. However, there is no explicit when-not guidance and no named alternative (e.g. make_printable, make_activity_pack); the agent must infer routing from the sibling names alone.

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

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