Skip to main content
Glama

write_prompt

Turns a short idea into a full video prompt by analyzing your uploaded image, using your configured Gemini or NVIDIA AI keys. Lets you generate AI video prompts quickly instead of writing them yourself.

Instructions

Turns a short idea ("the cat waves hello") into a full video prompt, looking at the uploaded picture. Uses the AI keys set up in OpenDaemon (Gemini or NVIDIA). You can also write the prompt yourself.

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": {
      "image": "<image>",
      "idea": "<idea>"
    },
    "name": "write_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
ideaYes
imageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the external-call and non-destructive profile is covered structurally. The description adds real context beyond that: it depends on the uploaded image and on AI keys being provisioned in OpenDaemon, which explains the openWorldHint. It does not say what happens when keys are missing, whether the call costs quota or how long it 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?

Two sentences, front-loaded with the transformation and followed by the configuration prerequisite and the self-write alternative. Nothing is redundant, though the parenthetical example could be trimmed without loss.

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?

With no output schema, the description should clarify what comes back — it implies a generated prompt string but does not say whether the result is returned to the caller or persisted somewhere the agent must then use. Given two required params and an external AI dependency, one more sentence on the return value and image format would make this complete.

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 0%, so the description carries the load for both required parameters. It does add meaning — "idea" is a short phrase like "the cat waves hello" and "image" is the uploaded picture — but it never specifies the format the image parameter expects (path, filename, URL or base64), which is a meaningful gap for a required input.

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?

The description names a concrete transformation (short idea → full video prompt) and a second input (the uploaded picture), which is specific enough to distinguish it from neighbors like build_video or add_text. It stops short of explicitly positioning itself against any sibling, but the verb+resource pairing is unambiguous.

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?

Usage is only implied: the closing line "You can also write the prompt yourself" signals this tool is an assistive/optional path for producing a prompt. A genuine prerequisite is stated (AI keys configured in OpenDaemon via Gemini or NVIDIA), which is useful context for deciding whether to call it, but there are no explicit when-not conditions or named alternative tools.

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