Skip to main content
Glama

Draw giveaway winner

giveaways_draw_winner

Draw a random winner from a StreamElements giveaway's entrants using its ID; call again to pick additional winners.

Instructions

Draw a random winner from the giveaway's entrants. Each call draws another winner.

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": {
      "giveawayId": "<giveawayId>"
    },
    "name": "giveaways_draw_winner"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoStreamElements channel id (24-char hex). Defaults to SE_CHANNEL_ID or the channel that owns the token.
giveawayIdYesGiveaway id (24-character hex id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, and the description usefully reinforces non-idempotency ("Each call draws another winner"), matching the annotation rather than contradicting it. However it omits whether the drawn entrant is removed from the pool, what happens when no entrants remain, or whether the winner is announced/notified — behavioral gaps beyond what the annotations cover.

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 sentences, front-loaded with the action, and the second sentence adds real (non-redundant) behavioral information about repeated calls. No waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with full schema coverage and annotations carrying the safety profile, and there is no output schema to explain. Still, an agent gets no signal about the return value (the winner identity) or the failure case of an exhausted entrant pool — both relevant for calling it correctly.

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 description coverage is 100%, with both channel and giveawayId fully documented (hex format, default behavior) directly in the schema. The description adds no syntax or constraint detail beyond it, 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?

Clear specific verb (draw) and resource (random winner from the giveaway's entrants). "Each call draws another winner" clarifies the repeatable nature. It does not compare itself to nearby siblings like contests_draw_winner or giveaways_list_entrants, but the core action is unambiguous.

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

Usage Guidelines2/5

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

The description implies repeat calls are normal ("Each call draws another winner") but never states when to use this versus contests_draw_winner or what to do first (e.g., giveaways_list_entrants). No prerequisites, no exclusions, no alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools