Printablesmith

Bingo cards

make_bingo_cards

Read-onlyIdempotent

Make printable bingo cards, every card different, with a call list. mode "words" for any theme or vocabulary; "pictures" for children who cannot read yet (picture names, or a picture_group); "numbers" for classic 1 to 75 bingo; "find_someone_who" for icebreaker human bingo (each square is something a person might have done, e.g. "has a pet"). Up to 100 cards.

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

Input Schema

Name	Required	Description
`mode`	No	What goes in the squares: words, pictures, numbers, or find_someone_who.
`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.
`cards`	No	How many different cards.
`items`	No	The words for the squares (words, find_someone_who), or picture names for picture bingo. Give more than the squares on a card (24 for 5 × 5) so cards differ: 30 to 40 is best.
`large`	No	Bigger, bolder words for young children and beginning readers (for older eyes, use large_print).
`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. "Thanksgiving Bingo". Keep it short.
`call_list`	No	A call list to cut out and draw from, at the end.
`grid_size`	No	Squares per side: 3, 4 or 5. Picture bingo is usually 3 or 4.
`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.
`free_space`	No	A free space in the middle of 3 × 3 and 5 × 5 cards (on unless turned off).
`large_print`	No	Large print for older eyes or low vision: bigger, bolder letters and roomier layouts (sizes are capped to fit). For young children, use large.
`dyslexia_font`	No	Print in OpenDyslexic, a typeface some readers with dyslexia find easier.
`picture_group`	No	Picture bingo: use a whole group of the site’s pictures instead of (or as well as) items.
`picture_names`	No	Picture bingo: print each picture’s name under it.
`picture_style`	No	Picture bingo: color or mono (black and white, to save ink).
`cards_per_page`	No	Cards on each page: 1, 2 or 4.

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.4/5.0

Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world generation call, so the safety burden is lifted. The description adds real behavioral context beyond that: the 100-card cap and the seed contract ("pass the seed from an earlier result to keep that version while changing other settings"), which tells the agent how reproducibility works. It does not describe output layout or download/return format, though an output schema exists.

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?

The core purpose is front-loaded and the mode list is compact despite covering four options. The second half is a dense run of settings guidance, but every sentence carries information rather than restating parameter names.

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 17-parameter, all-optional generator with an output schema and full annotation coverage, the description supplies the missing decision logic: which mode, how many items to supply, which accessibility flags to pick, and how seeds work. An agent has enough to call this correctly on the first attempt.

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%, so 3 is the baseline, but the description earns more by explaining how to use items well ("Give more than the squares on a card (24 for 5 × 5) so cards differ: 30 to 40 is best") and by disambiguating large vs large_print by audience. These are usage rules the schema cannot express.

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?

Opens with a specific verb and resource ("Make printable bingo cards") plus the differentiators that matter: every card is different and a call list is included. The four modes are then defined in one clause each, so an agent can tell this apart from make_word_search or make_crossword without opening the 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?

Mode selection guidance is unusually good: "words" for themes/vocabulary, "pictures" for children who cannot read, "numbers" for classic 1-75, "find_someone_who" for icebreakers. It also points at find_printables for theme names. It stops short of saying when to choose bingo over the other printable generators, so it falls one step below explicit alternative routing.

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?