Skip to main content
Glama

Plunder & Riffle Meme Engine

Presentation video

create_present

Telegram /present. 16:9 Joe presentation. ONE of topic, script, or audio_url. Poll get_job_status (sitdown); request_mp4 orientation "landscape". 25 credits ($0.25; BYOK $0.01).

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_present"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoawareness (default) or conversion
topicNo
lengthNotopic only
scriptNo
templateNo
audio_urlNohttps mp3/wav/m4a/mp4, ≤24 MB

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare destructiveHint=false, so the description carries most of the burden and delivers: the job is asynchronous (poll get_job_status), the cost is 25 credits / $0.25, BYOK is $0.01, and the output aspect ratio is 16:9. It omits what happens on failure or how long generation typically takes.

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?

Five dense clauses, front-loaded with the identity and the key input rule, with no filler. Some telegraphic fragments ('sitdown', 'Joe') are terse to the point of being cryptic, but nothing is wasted.

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?

For a six-parameter async generation tool with no output schema, the description covers the input constraint, the async polling path, the delivery call, pricing, and output orientation. Only the meaning of template and expected job duration/failure behavior are left out.

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 50%, and the description adds the genuinely useful mutual-exclusivity constraint across topic/script/audio_url. However, template (five enum values) and the intent of game remain undocumented in the description beyond the schema's own hints, so it only partially compensates.

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?

It states a concrete resource and format (a 16:9 presentation video) plus the Telegram /present entry point, so the agent can tell this apart from siblings like create_infomercial or create_whiteboard_pitch. 'Joe presentation' is brand shorthand rather than a plain description of the artifact, which costs a little clarity.

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 gives a hard input rule ('ONE of topic, script, or audio_url') and the follow-up sequence (poll get_job_status, then request_mp4 with orientation 'landscape'). It does not say when to choose this versus the many other create_* video tools, but it does name the correct post-call alternatives.

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