Skip to main content
Glama

Get latest lottery results

get_latest_results
Read-onlyIdempotent

Get the most recent official results (draw date, winning combination, complementary numbers and jackpot when applicable) of one game, newest first. Use it for questions like "what were the last Euromillones numbers?". Returns up to the 3 most recent draws.

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_latest_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesGame slug. Call list_games to see them all. Example: "euromillones".
limitNoHow many recent draws to return (1-3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add substance. It does: the response contents, newest-first ordering, and the cap of three draws, which is the kind of return-shape detail an agent needs given there is no 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.

Conciseness5/5

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

Three short sentences: what is returned, when to use it, and how many. The most useful information leads, and nothing is repeated or padded.

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?

With no output schema, the description carries the return-shape burden and does so by listing the fields returned. The only soft spot is 'returns up to the 3 most recent draws' versus a schema default of limit=1, which could leave an agent unsure what it gets by default.

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%, so both parameters are already documented, including the enum values and the 1-3 range for limit. The description's 'up to the 3 most recent draws' merely restates the schema maximum rather than adding format or selection meaning, so the baseline of 3 applies.

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 gives a specific verb and resource ('Get the most recent official results ... of one game') and enumerates the payload (draw date, winning combination, complementary numbers, jackpot). It also states ordering ('newest first'), which separates it implicitly from get_next_draw, though no sibling is named.

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?

The example question ('what were the last Euromillones numbers?') anchors the intended use clearly and shows the game parameter in practice. There are no explicit exclusions or named alternatives, so an agent must still infer that get_next_draw covers future draws and check_numbers covers ticket checking.

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