Skip to main content
Glama

Check whether a wallet can enter the current draw

luckdrop_check_entry
Read-only

Answer 'can this wallet enter the draw right now, and what exactly does it send'. Sourced from the CHAIN rather than our database, because this gates a transaction and a stale yes costs the caller gas on a revert.

Returns canEnter, a reason mirroring the contract's own revert strings, and the exact transaction to send. Entry is free -- the entrant pays only gas. Call this before sending an entry, every time.

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

Input Schema

NameRequiredDescriptionDefault
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. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses the data source (live chain, not the database) and the reason for that choice (a stale yes costs the caller gas on a revert), which is exactly the kind of failure-mode context annotations cannot carry. It also states the safety model plainly — unsigned transaction only, the service never signs or holds keys, the user sends it from their own wallet, and once mined it cannot be undone. The readOnlyHint=true is consistent here since the tool itself writes nothing, though the description could have said so explicitly to preempt confusion about a call that hands back a transaction.

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?

The answer-shaped purpose is front-loaded in a single quoted line, followed by source rationale, return contents, the call-before-send rule, and the custody/mutability caveats. Every sentence adds a decision-relevant fact and none restates the name or the schema.

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, so the description carries the return contract itself and does: canEnter, a reason mirroring the contract's revert strings, and the exact unsigned transaction to send. Combined with the single, fully described input and the explicit safety and finality warnings, an agent has everything needed to call this correctly and to advise the user afterward.

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% with a single fully documented address parameter, so the baseline would be 3. The description adds real meaning around it: 'this wallet,' and the cost model ('Entry is free -- the entrant pays only gas'), which tells the agent what the returned transaction's value should look like and sets the expectation for the user before they sign.

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?

Opens with a precise framing: 'can this wallet enter the draw right now, and what exactly does it send' — a specific verb (check entry eligibility + build the entry transaction) on a specific resource (a wallet's entry into the current draw). This is clearly distinct from the sibling set (check_prize, get_draw, get_results, list_market), none of which gate an entry transaction.

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?

Gives an explicit imperative and cadence: 'Call this before sending an entry, every time.' That is strong when-to-use guidance. It stops short of naming a when-not condition or an alternative tool to consult in a different situation, so it is not a full 5.

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