Skip to main content
Glama

Check numbers against a draw

check_numbers
Read-onlyIdempotent

Check whether a set of numbers won in one of the 3 most recent draws of a game (default: the latest). For "nacional" the numbers are décimo numbers (up to 5 digits, at most 5, pass them as strings to keep leading zeros, e.g. "01755"). For the other games pass the main numbers and, when the game has them, the extra numbers (stars, reintegro, clave...). Returns matches, whether it is a winner and the prize. Only the 3 most recent draws can be checked.

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": {
      "game": "<game>",
      "numbers": "<numbers>"
    },
    "name": "check_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesGame slug. Call list_games to see them all. Example: "euromillones".
numbersYesMain numbers to check (nacional: décimo numbers, up to 5 digits).
drawDateNoOptional draw date (YYYY-MM-DD). Must be one of the 3 latest draws; defaults to the latest.
extraNumbersNoOptional extra numbers: Euromillones stars, reintegro in Primitiva/Bonoloto, etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and not open-world. The description adds meaningful behavior beyond that: the 3-draw limit, the return fields (matches, winner status, prize), and game-specific input handling. It does not cover error behavior or rate limits, so it stops short of 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 description is four sentences and front-loads the purpose and draw limit before game-specific details. It is efficient overall, though the '3 most recent draws' limit is stated twice, which is a minor redundancy.

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 4-parameter tool with no output schema, the description covers purpose, scope, special 'nacional' handling, return summary, and the 3-draw constraint well. It does not mention list_games or elaborate on drawDate beyond the schema, but those are already covered by the 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, but the description adds useful meaning not fully captured by the schema: for 'nacional', numbers are décimo numbers up to 5 digits, at most 5, and should be passed as strings to preserve leading zeros. It also explains that other games may take main plus extra numbers (stars, reintegro, clave).

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 resource: check numbers against one of the 3 most recent draws, with a clear default and scope. It is distinguishable from siblings like get_latest_results because it evaluates user-supplied numbers rather than listing results.

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 purpose implies when to use it, and it gives a hard constraint ('Only the 3 most recent draws can be checked'), but it does not explicitly compare with or route to alternatives such as get_latest_results or get_next_draw. Usage is inferable rather than guided.

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