Skip to main content
Glama

Get the next lottery draw

get_next_draw
Read-onlyIdempotent

Get the next scheduled draw of one game: date, status and announced jackpot when available. Use it for "when is the next Primitiva draw and how much is the jackpot?".

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

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.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description contributes one genuine behavioral nuance, that the jackpot is only returned 'when available', but says nothing about failure modes for an unscheduled game or the shape of the response.

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?

Two sentences, zero waste: the core behavior and its return fields come first, followed by the intent routing. Nothing is padded or repeated from the title.

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 single-parameter tool whose annotations carry the safety profile, the definition is nearly sufficient, and the mention of returned fields compensates for the missing output schema. The only real gap is the lack of any signal distinguishing it from get_latest_results.

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 the single enum parameter is already documented with an example and a pointer to list_games. The description only reinforces 'one game', adding no syntax or constraint meaning beyond the schema, so the baseline 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?

States a specific verb and resource ('Get the next scheduled draw of one game') and enumerates what comes back: date, status and announced jackpot. The purpose is unmistakable, but it never identifies how it differs from the sibling get_latest_results, leaving that distinction to inference.

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?

Supplies a concrete usage framing — the quoted user question about 'when is the next Primitiva draw and how much is the jackpot' — which tells the agent exactly which intent maps here. It gives no explicit exclusions or named alternatives, so the when-not side is absent.

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