Skip to main content
Glama

Write a prompt with the local language model

enhance_prompt

Turn a short idea in any language into a detailed English prompt for image generation, editing, or video targets. Add an optional image reference for image-based targets.

Instructions

Turns a short idea (any language) into a detailed English prompt for a target: "Generate image", "Edit image", "Text to video (LTX)", "Image to video (LTX)" or "Wan camera move". Optional image (gallery id or path) for image-based targets. large=true uses Qwen 3.5 9B instead of Gemma 4 E2B. Takes 1 to 4 seconds. You may also write prompts yourself; this is a helper.

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

Input Schema

NameRequiredDescriptionDefault
ideaYes
imageNo
largeNo
targetNoGenerate image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses language normalization to English, that the operation is a non-destructive text helper, a concrete latency band ('Takes 1 to 4 seconds'), and which model backs each mode (Qwen 3.5 9B vs Gemma 4 E2B). It does not cover failure behavior for unknown targets or whether the result is length-bounded.

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?

It is a single dense paragraph with the core transformation front-loaded, followed by options, then latency, then the routing caveat. Every sentence carries information; the telegraphic fragment style ('large=true uses ...') is efficient rather than padded.

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 four-parameter tool with no annotations, no output schema, and zero schema coverage, the description supplies transformation semantics, all parameter meanings, model choice, and latency. The return value is implied ('a detailed English prompt') rather than specified, but that is the only meaningful omission.

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 0%, so the description must supply all parameter meaning and largely does: idea (short, any language), image (gallery id or path, only for image-based targets), large (model swap with both model names), and target (with five enumerated values and the default restated implicitly as 'Generate image'). The only gap is that it never says precisely which of the five targets accept an image.

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 gives a specific verb-plus-resource: it converts a short multilingual 'idea' into a 'detailed English prompt', and it enumerates the five target styles it can produce for. That makes clear it emits text rather than media, which implicitly separates it from siblings like generate or figures, but no sibling is actually named, so an agent must infer the boundary.

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 states the trigger condition (you have a short idea and need a detailed prompt), the conditional sub-case ('Optional image ... for image-based targets'), and an explicit alternative ('You may also write prompts yourself; this is a helper'). It stops short of saying which target to pick in a given situation or when to prefer a sibling generation tool directly.

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