Skip to main content
Glama

Zovo Bingo Card Maker

Generate goal bingo card

generate_goal_bingo
Read-onlyIdempotent

Use this when the user wants a goal bingo card (new year goal bingo, 2027 bingo card, resolutions bingo, bucket-list bingo): one personal 5x5 card (or 4x4, 3x3) of their own goals with a free centre, title, year and theme colour, as a PNG, SVG and printable PDF. Goals marked completed print with a check mark and the tool counts bingo lines. Needs one goal per square (24 for 5x5 with a free centre). Does not invent goals for the user and does not make sets of party cards (use generate_bingo_cards).

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": {
      "goals": "<goals>"
    },
    "name": "generate_goal_bingo"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoShuffle number from an earlier result to repeat the same order, e.g. 77.
yearNoYear for the title, e.g. 2027 gives "2027 Bingo".
goalsYesThe goals, one per square, e.g. ["Run a 10K", "Read 12 books", "Learn to make sourdough"]. Exactly 24 for a 5x5 card with a free centre (25 without), 16 for 4x4, 8 for 3x3 with a free centre (9 without). Up to 80 characters each.
paperNoPaper size for the PDF, e.g. letter (default) or a4.
titleNoCard heading, e.g. Maya's 2027 Bingo. Overrides the year title.
shuffleNotrue to mix the goals into a random order, e.g. false (default keeps your order, filled row by row).
subtitleNoSmall line under the title, e.g. One square at a time.
completedNoGoals already done, written as in goals, e.g. ["Read 12 books"]. They print with a check mark and count toward bingo lines.
grid_sizeNo3, 4 or 5 (default 5), e.g. 5.
free_spaceNoFree centre square on 3x3 and 5x5 cards, e.g. true (default).
accent_colorNoTheme colour as hex or a name, e.g. #0B7285, teal, gold, purple. Default raspberry #C2255C.
center_labelNoText in the centre square, e.g. FREE (default), Be kind to myself, or 2027.

Output Schema

NameRequiredDescriptionDefault
doneYes
seedYes
viewYes
cellsYes
titleYes
accentYes
subtitleYes
warningsYes
downloadsYes
grid_sizeYes
done_countYes
goal_countYes
bingo_linesYes
center_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description still adds real behavior beyond them: three output formats, that completed goals print with a check mark, that bingo lines are counted, and that the tool refuses to invent goals. It stops short of saying where files land or how the response is shaped, but that is largely covered by the output schema.

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 trigger condition is front-loaded, and the synonym list ('new year goal bingo, 2027 bingo card, resolutions bingo, bucket-list bingo') materially aids retrieval rather than padding. The sentence is long and densely parenthesised, but no clause is pure filler.

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 12-parameter generation tool, the description covers the artifact type, output formats, square-count constraint, completion rendering and the sibling boundary; the output schema and full-coverage input schema handle the rest. Only file destination / response shape is left unstated, which is minor given the output schema exists.

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% and every parameter carries its own example and default, so the schema does the heavy lifting. The description restates a few of these (grid size options, free centre, one goal per square with the 24-count) without adding syntax or constraints the schema lacks. Baseline 3 is appropriate.

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 a specific verb+resource ('goal bingo card'), enumerates the concrete artifact (one personal 5x5/4x4/3x3 card with free centre, title, year, theme colour, in PNG/SVG/PDF), and explicitly distinguishes it from the sibling generate_bingo_cards (party card sets). An agent can route 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 Guidelines5/5

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

It opens with an explicit trigger ('Use this when the user wants a goal bingo card...'), lists query phrasings that should route here, and states an exclusion with the named alternative ('does not make sets of party cards (use generate_bingo_cards)'). When-to-use and when-not-to-use are both covered.

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