Skip to main content
Glama

Enhance prompt

enhance_prompt
Read-only

Rewrite a prompt the way the studio's prompt improver does. kind: image | video.

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

Input Schema

NameRequiredDescriptionDefault
kindNoimage
promptYes
model_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds that the rewrite matches the studio's own improver, which is mild context. It does not say whether the original prompt is preserved, how deterministic the rewrite is, or what role model_id plays — with an output schema present, the return shape is at least documented elsewhere.

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 short sentences, front-loaded with the core action, no filler. The brevity is efficient rather than padded, though it edges toward under-specification rather than crispness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with zero schema description coverage, the definition leaves the required `prompt` argument and the optional `model_id` undocumented, and gives no hint about the relationship between enhancing a prompt and the generate-family siblings. The presence of an output schema and read-only annotations reduces the burden, but not enough to 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% and the `kind` property has no enum in the schema, so the description's '`kind`: image | video' is genuinely additive — it supplies the only enumeration of valid values. However, `prompt` (the required input) and `model_id` are left completely unexplained, so the compensation for the coverage gap is only partial.

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?

States a specific verb and resource — 'rewrite a prompt' — and adds that it mimics the studio's prompt improver, which tells an agent this is a prompt-transformation tool rather than a generation tool. It never names or contrasts any sibling (e.g. generate, estimate_cost), so differentiation is implied by the verb only.

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?

There is no guidance on when to call this versus generating directly, no stated prerequisite that a prompt exists, and no note on what to do with the result (e.g. pass it to generate). The only usage-ish signal is the inline mention of `kind` values.

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