Skip to main content
Glama
Sign In

Perkadoo

by com.perkadoo
OverviewDiscussionsAdmin

Pick winners from a post's comments

draw_from_post

Pick random winners from the people who commented on a public post, from its link, with no account: YouTube videos, Bluesky posts and Reddit threads. Each commenter gets one entry. Reads the comments and draws in one step, with public drand randomness anyone can check. Returns the winners and a public results link to share. An Instagram post needs its owner: the answer is a link for them.

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": {
      "link": "<link>"
    },
    "name": "draw_from_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe post's link, as copied from its share button: a YouTube video, a Bluesky post or a Reddit thread.
titleNoA name for the giveaway, shown on the results page. Default: the post's title.
methodNosingle: one winner. multiple: several equal winners. placed: 1st, 2nd, 3rd… with a prize per place.single
prizesNoPrize labels. For placed draws, one per place in order; otherwise one prize for every winner.
winnerCountNoHow many winners to pick.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only flag non-read-only, open-world, non-idempotent, non-destructive; the description adds real value on top: no account required, one entry per commenter, public verifiable drand randomness, one-step read-and-draw, and a shareable results link in the response. It stops short of saying what happens on redraws or private/unsupported posts, but it is well above the annotation bar.

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?

Front-loaded with the core action and platform list, and every sentence carries information (entry rule, randomness, return value, Instagram fallback). Phrasing is slightly rambling ('from its link, with no account: ...' and the dangling 'the answer is a link for them'), costing a point.

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?

With five parameters and no output schema, the description correctly supplies the return contract (winners plus a public results link) and the platform/account constraints. Remaining gaps — failure modes like private posts, or whether a redraw creates a new record — are minor for this tool's complexity.

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 enum meanings for method and the prize-label rules are already documented in the schema. The description only reinforces that the link is a post link and that commenters form the entry pool, without adding syntax or format detail beyond structured fields — baseline 3.

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 and resource ('Pick random winners from the people who commented on a public post') plus the supported surfaces (YouTube, Bluesky, Reddit). The one-step read-and-draw framing separates it from read_post_comments (read only) and draw_winners (presumably entry/giveaway based).

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?

Implied context is clear: use when you have a public post link and want a draw without an account. But no sibling is named and no explicit when-not is given, aside from the Instagram note that the owner must act; an agent still has to infer when to prefer draw_winners or create_giveaway instead.

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

All Perkadoo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources