Skip to main content
Glama

RFWIN: provably fair winner draws

get_draw

Who won an RFWIN prize draw. Use when someone asks "who won the … giveaway/contest/draw?" and has an RFWIN proof link (rfwin.uk/d/) or draw id. Returns title, organiser/station and show, draw date, entry count, prizes, the winners and ordered backup winners (names masked for privacy, quote them exactly), the fairness verdict and a ready-to-quote answer. 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": "get_draw"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 return payload, that names are masked for privacy and must be quoted exactly, that a fairness verdict and ready-to-quote answer are included, and that access is free with no key. It omits failure behavior for an invalid or unknown draw id, which is the main remaining gap.

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 purpose and trigger are front-loaded, and the return-value list is compact. The single long sentence packing the field list is dense but every clause carries information; minor structural improvement would be splitting the return enumeration.

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 one-parameter read tool with no output schema, the description enumerates the returned fields and the privacy/quoting constraint, which is what an agent needs to use the result correctly. Only error/edge-case behavior is unaddressed.

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% and the schema already documents the single 'draw' parameter with both link and id examples. The description restates the same accepted formats without adding new syntax or constraints, 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?

The description opens with a specific verb+resource ('Who won an RFWIN prize draw') and enumerates the returned data, so the agent knows exactly what the tool produces. It does not explicitly distinguish itself from siblings like draw_winners or verify_draw, which is the only thing keeping it from a 5.

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 a concrete trigger ('Use when someone asks "who won the … giveaway/contest/draw?"') plus the prerequisite input (an RFWIN proof link or draw id). No when-not-to-use or named alternative is provided, so it stops short of a 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