Skip to main content
Glama

Get one LuckDrop draw's rounds and winner

luckdrop_get_results
Read-only

Read a single draw's five rounds and its winner.

week is the DISPLAY week number by default. If you are following contractWeekId from the chain, pass idSpace='contract' -- the same number means different draws in the two id spaces, and without it you get a valid-looking answer describing the WRONG draw. The response echoes back which space it used, plus both ids.

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": {
      "week": "<week>"
    },
    "name": "luckdrop_get_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekYesThe draw number to read.
idSpaceNoWhich numbering the `week` argument is in. Defaults to display.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / week / maximum
      Added value: +10000
    • addedInput schema / properties / week / minimum
      Added value: +1
    • changedInput schema / properties / week / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the critical non-obvious behavior that a mismatched id space yields a valid-looking but wrong response, plus the fact that the response echoes the id space and both ids. It does not mention rate limits or auth needs, but the id-space trap disclosure is significant added context.

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 short paragraphs, the purpose front-loaded before the id-space warning, and no filler. The caution about getting the WRONG draw is the right thing to emphasize.

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?

For a two-parameter read tool with no output schema, the description covers what is returned (five rounds, winner, echoed id space and both ids) and the one trap that causes incorrect results. Nothing an agent needs in order to call it correctly is missing.

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 the baseline would be 3, but the description goes further by explaining why idSpace matters: the same integer denotes different draws in each space. That consequence-level meaning is not in the schema's neutral enum description.

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 and resource: reading one draw's five rounds plus its winner, which is narrower than a generic draw lookup. It does not explicitly name a sibling it replaces, but the 'five rounds and winner' framing makes its scope distinct enough to select without opening other schemas.

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 an explicit conditional rule: if the caller is following contractWeekId from the chain, pass idSpace='contract'. That is actionable when-to-use guidance with a stated failure mode, though it stops short of naming an alternative tool for related lookups.

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