Skip to main content
Glama

Plunder & Riffle Meme Engine

Best-of reel from links

create_best_of

The /sitdown bestof command: 1–5 temp pages or direct media links play, silent, on the sidekick's screen while the host counts them down — one voiced best-of reel. Give links and an optional theme. 25 credits ($0.25; BYOK: $0.01), refunded on failure. Async: poll get_job_status (kind sitdown), 1–2 min. Done carries pageUrl (a preview, no MP4): show it; request_mp4 only after the human approves.

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": {
      "links": "<links>"
    },
    "name": "create_best_of"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksYes1–5 https links: a temp page (/m/<id>) or a direct .mp4/.gif/.png. A whitespace-separated string works too.
sceneNoThe set (default: the owner's saved one).
themeNoOptional theme the countdown hangs on, e.g. "job hunt fails" (≤120 chars).
outfitNoDefault: the brand's look.
languageNoDefault English.
accessoryNo2–5 words on the host's shirt (≤40 chars). Implies outfit: tee.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With only destructiveHint=false in annotations, the description carries real behavioral weight: 25 credits ($0.25; BYOK $0.01) refunded on failure, async completion in 1–2 minutes, and a hard rule that the finished job returns a preview pageUrl with no MP4 until request_mp4 is called post-approval. That is a lot of useful context, though it doesn't cover what failure states or credit refund timing look like in practice.

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 content is front-loaded (what it does, then inputs, then cost, then async/return handling) and no sentence is filler. The telegraphic, dash-heavy style is dense to the point of being slightly cryptic on a first read, which keeps it off a 5.

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?

For an async, credit-charged generation tool with no output schema, the description supplies everything an agent needs: inputs, cost and refund policy, expected latency, the polling tool and kind, and what the done payload does and does not contain. Nothing material to correct invocation is missing.

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%, so the baseline is 3, but the description adds a bit: it describes `links` as media that plays on screen (reinforcing the 1–5 limit) and frames `theme` as optional, matching the schema's own guidance. The remaining four parameters (scene, outfit, language, accessory) are left entirely to the schema, which already documents them well.

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?

The description names a specific verb+resource – turning 1–5 temp pages or direct media links into one voiced best-of reel via the /sitdown bestof command – and pins the scope (silent playback on the sidekick's screen, host countdown). It is distinguishable at a glance from campaign/pitch siblings, which produce different artifacts.

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 tells the agent exactly what to supply (links plus optional theme) and lays out the follow-up sequence: poll get_job_status with kind sitdown, show the pageUrl preview, and only call request_mp4 after human approval. What's missing is an explicit 'don't use this when…' exclusion versus the other create_* tools, so a 4 rather than 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