Skip to main content
Glama

Check a wallet's claimable LuckDrop prizes

luckdrop_check_prize
Read-only

Check whether a wallet has won a prize it has not yet collected, and get the transaction that claims it. Read from the chain, so it works for a wallet that entered without ever signing in to the website.

SCOPE: this reads THIS DEPLOYMENT's prize escrows, and the result names in escrowsChecked exactly which escrows it consulted. Contract week ids reset when the contracts are redeployed, so a prize sitting in an escrow from an EARLIER deployment is out of reach here and no weekId will find it.

With no weekId this scans the most recent 26 contract weeks on those escrows and tells you the exact range it covered. The claim window is 180 days from the award, so a prize older than that SCAN window may still be claimable -- pass an explicit weekId (the CONTRACT week id, which luckdrop_get_results reports) to reach an older week ON THOSE ESCROWS directly.

This returns an UNSIGNED transaction ({to, data, value}). This service never signs for the user and never holds keys. The user must approve and send it from their own wallet on Base, and once mined it CANNOT be undone.

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": {
      "address": "<address>"
    },
    "name": "luckdrop_check_prize"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekIdNoOptional CONTRACT week id, checked on its own instead of scanning. Reaches an older week on THIS deployment's escrows.
addressYesAn Ethereum address on Base, 0x followed by 40 hex characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / address / description
      Previous value: -"An Ethereum address on Base Sepolia, 0x followed by 40 hex characters."New value: +"An Ethereum address on Base, 0x followed by 40 hex characters."
  2. Changed3 schema fields changed
    • addedInput schema / properties / weekId / maximum
      Added value: +10000
    • addedInput schema / properties / weekId / minimum
      Added value: +1
    • changedInput schema / properties / weekId / type
      Previous value: -"number"New value: +"integer"
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the read source (on-chain), the exact return shape (an UNSIGNED {to, data, value} transaction), that the service never signs or holds keys, that the user must approve and send on Base, and that the mined claim CANNOT be undone. It also discloses a response field (escrowsChecked) that the agent can use to verify coverage. Minor gap: the 26-week default scan's cost/latency or failure modes are not described.

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 first sentence is front-loaded with the action and result, and the SCOPE paragraph is clearly separated so an agent can skim the constraint. It is longer than typical and repeats the 'THIS DEPLOYMENT / EARLIER deployment' point in two places, but each remaining sentence carries a distinct operational fact (week-id reset, 180-day claim window, unsigned transaction).

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?

There is no output schema, yet the description still states the return payload explicitly ({to, data, value}) and names the escrowsChecked field, so an agent knows both what it gets back and how to verify coverage. Combined with the deployment-scope and weekId-reach caveats, nothing needed to call this 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%, so the schema already documents both parameters and the baseline is 3. The description does add real meaning — weekId is the CONTRACT week id (as opposed to some other week numbering), it is checked on its own rather than scanning, and the no-weekId default is a 26-week scan — but it does not add anything about the address parameter beyond the schema pattern.

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 opening sentence gives a specific verb and resource: 'Check whether a wallet has won a prize it has not yet collected, and get the transaction that claims it.' It also implicitly separates itself from siblings by pointing at luckdrop_get_results as the source of contract week ids, and by scoping itself to prize escrows rather than entries or draws.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use is given ('works for a wallet that entered without ever signing in to the website'), plus an explicit when-to-use-the-parameter rule: pass weekId to reach an older week when the default 26-week scan is insufficient. It also states a clear limitation — prizes in escrows from an EARLIER deployment are out of reach and no weekId will find them — which is exactly the kind of negative guidance an agent needs.

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