Skip to main content
Glama

Plunder & Riffle Meme Engine

Jobless Joe reaction show

create_ridiculous

The /ridiculous command: one ~30s episode of Jobless Joe's meme reaction show — Joe roasts the topic in five scenes while Ralph acts it out on a giant TV. topic is a subject, a link (roasted as a website autopsy), a business, or "roast my competitor's ad". Optional format forces a segment. 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. Done also carries format and altEnding.

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": {
      "topic": "<topic>"
    },
    "name": "create_ridiculous"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesWhat the episode roasts (≤400 chars): a topic, a link, a business, or e.g. "roast my competitor's ad".
formatNoForce a segment. Default: picked from the topic (a link is a website autopsy).
languageNoDefault English.
alt_endingNoUse the episode's alternate last line instead of the main one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only supply destructiveHint=false, so the description carries the real behavioral load: 25 credits ($0.25, BYOK $0.01) refunded on failure, async execution at 1–2 minutes, and a human-approval gate before MP4 generation. It also discloses that the completed job carries a preview pageUrl with no MP4, which prevents an agent from promising a video file.

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?

Dense but front-loaded: the command, the output artifact, and the credit cost appear before the async and approval details. Some parentheticals ('a preview, no MP4', 'BYOK: $0.01') are compressed almost to the point of being cryptic, but no sentence is wasted.

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?

With no output schema, the description still covers the return surface (pageUrl, `format`, `altEnding`), the cost, the async polling path, and the timing window. For a four-parameter, credit-consuming generation tool, an agent has everything needed to call it and handle the result correctly.

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 real meaning: it clarifies that a link is roasted as a website autopsy and that `format` forces a segment rather than merely hinting at one. It also explains that `alt_ending` swaps the episode's last line, which the schema states only tersely.

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 and resource: it produces one ~30s episode of Jobless Joe's meme reaction show with five scenes and Ralph acting it out. That is concrete enough to distinguish it from the create_* siblings and from get_job_status/request_mp4, which are explicitly framed as follow-on steps.

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

Usage Guidelines5/5

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

It says exactly what counts as a valid `topic` (subject, link, business, or 'roast my competitor's ad'), when `format` should be forced, and that the link case defaults to a website autopsy. It also lays out the full workflow: poll get_job_status (kind sitdown), then call request_mp4 only after human approval, which routes the agent away from premature MP4 requests.

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