Skip to main content
Glama

Get aggregated game statistics

get_public_statistics
Read-onlyIdempotent

Aggregated statistics of a game over its last 2000 draws: most and least frequent numbers, longest absences, even/odd split, sum range and top pairs. Available for: primitiva, bonoloto, euromillones, gordo, eurodreams, lototurf. Covers the last 2000 draws only; no per-number tables or custom periods.

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>"
    },
    "name": "get_public_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesGame slug. Call list_games to see them all. Example: "euromillones".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description usefully adds the fixed 2000-draw window and the supported game set, which the annotations do not convey. It says nothing about response shape, ordering, or how absence/streak values are measured, so added behavioral depth is moderate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what it returns first, valid inputs second, scope limits last. Every clause earns its place and nothing is repeated padding.

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?

With no output schema, the description compensates by enumerating the statistics that come back, so the agent knows the return shape. Combined with the supported-game list and the explicit window/exclusion constraints, nothing needed to call this one-parameter tool correctly 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 coverage is 100%: the single 'game' parameter already carries an enum, an example, and a pointer to list_games. The description's list of supported games largely restates the enum, so it adds little meaning beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Aggregated statistics of a game') and enumerates exactly what is computed (frequency extremes, longest absences, even/odd split, sum range, top pairs), which makes it clearly distinct from per-draw tools like get_latest_results or check_numbers. It never names a sibling tool, so the differentiation is implicit rather than explicit.

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?

It gives concrete applicability ('Available for: primitiva, bonoloto, ...') and explicit exclusions ('Covers the last 2000 draws only; no per-number tables or custom periods'), which tells the agent when this tool is the wrong choice. It stops short of naming which tool to use instead for per-number or custom-period queries, so there is no full alternative routing.

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