Skip to main content
Glama

RFWIN: provably fair winner draws

verify_draw

Was an RFWIN prize draw fair. Recomputes the draw server-side: SHA-256 seed commitment, entry-list hash, the drand public randomness round (cross-checked against the drand network), draw digest, every win hash, and re-derives every winner from the entry list. Returns verdict (verified | verified_hash_level | partially_verified | mismatch | not_drawn_yet), each check with details, what verification does and does not prove, the hashes and a recipe to recompute it yourself. Free, no key.

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": {
      "draw": "<draw>"
    },
    "name": "verify_draw"
  }
}

Input Schema

NameRequiredDescriptionDefault
drawYesRFWIN proof link (e.g. https://rfwin.uk/d/xxlqh5ac9f) or the draw id

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?

With no annotations, the description carries the full burden and does well: it discloses the exact machinery (SHA-256 seed commitment, entry-list hash, drand round cross-checked against the network, draw digest, per-win hashes), the cost/auth profile (free, no key), and explicitly notes the response states what verification does and does not prove. It stops short of naming failure modes outside the verdict enum or discussing latency.

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 rhetorical 'Was an RFWIN prize draw fair' opener front-loads intent, and the rest is a single dense but information-bearing sentence with no filler. It is long and slightly run-on, but nearly every clause adds a distinct fact an agent would otherwise have to discover by calling.

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?

No output schema exists, and the description compensates fully by enumerating the verdict values (verified through not_drawn_yet) and listing the payload contents: per-check details, provenance caveats, hashes, and a recompute recipe. Nothing an agent needs in order to call or interpret the result 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?

One parameter at 100% schema description coverage, and the schema already explains both accepted forms (proof link or draw id). The description adds no further syntax, URL-handling, or error behaviour beyond that, so the baseline 3 applies.

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?

States a specific verb (recompute/verify) applied to a specific resource (RFWIN prize draw), and the scope is unambiguous: server-side recomputation of the whole draw, not a fetch. An agent can distinguish it from get_draw or draw_winners because the description makes clear this re-derives winners rather than returning stored results.

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

Usage Guidelines3/5

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

Usage is strongly implied — you call this to check whether a draw was fair rather than to see winners — but no alternative is named and no when-not-to-use condition is given. The 'Free, no key' note removes a practical gating question but is not routing guidance.

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