Skip to main content
Glama

Plunder & Riffle Meme Engine

Jobless Joe News

create_news

Telegram /joenews (not /news). Live sources. Desk/tv, 45–120s. mode or topic; short|standard|deep; language. Refunds if none answer. 25 credits ($0.25; BYOK $0.01). Poll get_job_status (sitdown): pageUrl, caption, sources. One outlet is reported. MP4 after approval.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoDefault general (top stories). Ignored with a topic.
pagesNo≤3 https pages that play on Joe's TV: temp /m/ page, .mp4/.gif/.png, here.now or plunderandriffle.com page.
topicNoReport on this instead (≤200 chars).
layoutNodesk (default): Joe + Phony showing each story's picture; tv: the giant TV.
lengthNo≈45s · ≈90s (default) · ≈2 min.
languageNoDefault English.
audio_urlNohttps mp3/wav/m4a that plays first; Joe reacts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations supply only destructiveHint=false, so the description carries the behavioral load and does so well: it discloses cost (25 credits / $0.25, BYOK $0.01), a refund policy when no source answers, an asynchronous job requiring polling of get_job_status, and an approval gate before the MP4 is produced. It also notes "One outlet is reported", which signals single-source output. It stops short of explaining what approval entails or where the MP4 lands, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Nothing is wasted, but the telegraphic fragment style is not front-loaded: it leads with channel routing instead of what the tool does, and lines like "Poll get_job_status (sitdown): pageUrl, caption, sources. One outlet is reported." are cryptic without prior context. Density is high but readability and ordering cost it.

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?

For a 7-parameter async media-generation tool with no output schema, the description does cover cost, async polling, refunds, approval, and the polled fields (pageUrl, caption, sources). However it omits a plain statement of what is produced and where, and the approval step is named without explanation, leaving gaps an agent would need to close.

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%, so the schema already documents every parameter, including defaults for mode, layout, and language. The description adds only length range ("45–120s") and the short|standard|deep naming, both of which are already in the schema. Baseline 3 applies since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states a clear verb+resource; it opens with a routing fragment ("Telegram /joenews (not /news)") and reads as a parameter/cost briefing. Only through cues like "Live sources", "Desk/tv, 45–120s" and "MP4 after approval" can an agent infer it produces a short news video segment. It does differentiate from the sibling it names (get_job_status is polling, not creation), but the core purpose is implied rather than stated.

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?

"Telegram /joenews (not /news)" is channel routing, not guidance on when to pick this tool over the many other create_* siblings. The only near-guidance is "mode or topic", which describes input selection rather than tool selection, and "Poll get_job_status" which is post-invocation workflow. No conditions, prerequisites, or alternatives are given for choosing create_news itself.

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