Skip to main content
Glama

Zovo Bingo Card Maker

Generate bingo cards

generate_bingo_cards
Read-only

Use this when the user wants printable bingo cards: a bingo card generator or bingo card maker for a holiday party, classroom, baby shower, team meeting, or any game with their own words or phrases, or classic number bingo (1-75) or UK 90-ball tickets. Makes 1-200 different cards (3x3, 4x4 or 5x5, free centre on or off) with each item spread evenly, optionally so that no two cards share a winning line. Returns card 1, balance and uniqueness numbers, and links to a cards PDF (1, 2, 4 or 6 per page, cut lines), a caller sheet PDF and a CSV. Does not add pictures, and does not draw items or check claims (use show_bingo_caller). Not for a single personal goals card (use generate_goal_bingo) or for prize or money games.

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": "generate_bingo_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNowords (default): your own words or phrases. numbers_75: classic US bingo, 5x5 with B 1-15, I 16-30, N 31-45, G 46-60, O 61-75. numbers_90: UK-style 3x9 tickets with 15 numbers from 1-90, printed in strips of 6. Example: words.
seedNoCard set number from an earlier result, e.g. 4242. The same items, options and seed always rebuild the same cards. Leave out for a new random set.
itemsNoFor mode words: the words or phrases to put on the cards, one per entry, e.g. ["Ugly sweater", "Mistletoe", "Hot cocoa"]. Need at least 24 for 5x5 with a free centre, 25 without, 16 for 4x4, 8 or 9 for 3x3. Up to 300, each up to 100 characters.
paperNoPaper size for the PDFs, e.g. letter (default) or a4.
titleNoHeading printed on every card, e.g. Holiday Party Bingo. Default Bingo.
grid_sizeNoCard size for mode words: 3, 4 or 5 (default 5), e.g. 5. Classic numbers_75 is always 5x5; numbers_90 tickets are always 3x9.
card_countNoHow many different cards (or tickets) to make, 1-200, e.g. 30. Default 30.
free_labelNoText in the free centre square, e.g. FREE (default), Santa, or Baby.
free_spaceNoFree centre square on 3x3 and 5x5 cards, e.g. true. Default true for 5x5 and false for 3x3; 4x4 cards have no centre.
accent_colorNoTheme colour as hex or a name, e.g. #2B8A3E, red, green, gold, pink, purple, teal, christmas. Default raspberry #C2255C.
unique_linesNotrue = no two cards share an identical winning line (row, column or diagonal), so two players never complete the very same line. Needs enough items; the tool explains if the request is not possible. Default false (cards are always all different).
cards_per_pageNoCards per printed page: 1, 2, 4 or 6, e.g. 2. Default 2 (6 for 90-ball tickets). Pages get dashed cut lines.

Output Schema

NameRequiredDescriptionDefault
gridYes
modeYes
seedYes
viewYes
titleYes
card_1Yes
balanceYes
warningsYes
downloadsYes
pdf_pagesYes
card_countYes
free_labelYes
free_spaceYes
item_countYes
uniquenessYes
caller_argsYes
cells_per_cardYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: it discloses what comes back (card 1, balance and uniqueness numbers, PDF and CSV links), the print layout behavior (cut lines, cards per page), and hard limitations ('does not add pictures, and does not draw items or check claims'). It also explains the failure mode of unique_lines ('the tool explains if the request is not possible') and that cards are always all different even when the flag is off.

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?

Front-loaded with the trigger condition and the exclusions come last, which is the right order. It is dense and runs long as a single sprawling sentence list, but nearly every clause carries a distinct fact (modes, counts, outputs, limits), so little is wasted.

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 12-parameter tool with no required params, the description covers modes, scale limits, print output, determinism via items+options+seed, and explicit scope exclusions. With an output schema present it does not need to detail return values, yet naming the outputs still helps the agent set expectations; nothing essential 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 every parameter is already documented with examples and defaults; the description's parameter-adjacent content (1-200 cards, 3x3/4x4/5x5, free centre on/off, 1/2/4/6 per page) largely restates the schema rather than adding new semantics. Baseline 3 applies; the description's main added value is the interaction between item count and grid size, which the schema also covers.

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+resource ('generate printable bingo cards') and immediately enumerates the supported variants: custom words, classic 75-ball numbers, UK 90-ball tickets. It explicitly distinguishes itself from both siblings by name ('use show_bingo_caller', 'use generate_goal_bingo'), so an agent can pick it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with 'Use this when the user wants printable bingo cards' and lists concrete triggering contexts (holiday party, classroom, baby shower, team meeting). It also gives explicit when-not guidance with named alternatives for single personal-goals cards and prize/money games, and routes caller/claim-checking to show_bingo_caller.

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