Skip to main content
Glama

Zovo Bingo Card Maker

Show bingo caller

show_bingo_caller
Read-only

Use this when the user is running a bingo game: call or draw the next word or number at random, show what has been called on a big screen, check whether a claimed bingo on card number N is real (which line, at which call, and who won first), or list all cards that have bingo now. Pass the same items and the caller_args (mode, grid_size, free_space, card_count, seed, unique_lines) from generate_bingo_cards, plus everything called so far in order. Draws use secure randomness. Does not make or print cards and does not keep game state between calls: always send the full called list. Not for prize, betting 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": "show_bingo_caller"
  }
}

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.
titleNoGame title shown on the caller screen, e.g. Holiday Party Bingo.
actionNodraw (default): call the next item at random. check: verify a claimed bingo on card_number. winners: list every card that has the pattern now. board: show what has been called. Example: check.
calledNoEverything already called, in call order, exactly as shown on the cards, e.g. ["Mistletoe", "Hot cocoa"] or ["B-12", "N-40", "O-71"]. Empty for a new game.
patternNoWinning pattern to check, e.g. line. line: any row, column or diagonal (90-ball: any row). two_lines: two complete lines. four_corners: the 4 corner squares (not for 90-ball). full_card: every square (full house). Default line.
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.
list_codeNoFor word games: list_code from caller_args of generate_bingo_cards, e.g. 0k3x9qa. Confirms the items were sent in the same order as when the cards were made, so card numbers match.
card_countNoHow many different cards (or tickets) to make, 1-200, e.g. 30. Default 30.
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.
card_numberNoFor action check: the card number printed on the claimed card, e.g. 17.
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).

Output Schema

NameRequiredDescriptionDefault
modeYes
viewYes
checkYes
titleYes
actionYes
calledYes
currentYes
patternYes
winnersYes
remainingYes
caller_argsYes
total_itemsYes
called_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=false, but the description adds genuinely non-obvious behavior: draws use secure randomness, the tool is stateless between calls, and the full called list must be resent every time. It does not cover seeding/reproducibility of draws or rate/limit behavior, so it stops short of a 5.

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 usage trigger is front-loaded and the statelessness constraint follows immediately, so the important calls sit early. The first sentence is a long multi-clause list of actions, which is dense but each clause maps to a real mode.

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 13-parameter, four-action tool with an output schema, the description covers the cross-tool contract, statelessness, randomness, and scope exclusions. Remaining detail (per-action parameter requirements, what board/winners return) is carried by the schema and output schema.

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 baseline is 3; the description earns above that by tying mode, grid_size, free_space, card_count, seed and unique_lines to their origin in generate_bingo_cards and by stating the ordering contract for 'called' and 'items'. It leaves list_code and card_number to the schema.

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 names the concrete operations (draw the next item, show what has been called, check a claimed bingo on card N, list all winning cards) and explicitly scopes out card creation, which separates it cleanly from the sibling generate_bingo_cards.

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?

It states the triggering situation ('when the user is running a bingo game'), points to generate_bingo_cards as the source of items and caller_args, and gives an explicit exclusion ('Not for prize, betting or money games'). An agent has no ambiguity about when to pick this tool.

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