Skip to main content
Glama

Prompt Booster

prompt_booster

Enhances prompts with AI guides tailored to a chosen deAPI model and inference type, helping image, video, audio, and embedding requests align with the target workflow.

Instructions

Enhance a prompt using AI guides tailored to a specific deAPI model + inference type.

Synchronous — returns the enhanced prompt(s) directly. Charged per call; use prompt_booster_price first if you want a quote.

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>",
      "type": "<type>",
      "model_slug": "<model_slug>"
    },
    "name": "prompt_booster"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesInference type the enhanced prompt is intended for, in v2 dot notation (e.g., 'images.generations', 'videos.animations', 'audio.speech').
imageNoOptional reference image as URL, data URI, or base64. Required for type='images.edits' and 'videos.animations'. Supported formats: JPEG, PNG, BMP, GIF, WebP.
promptYesThe prompt to enhance.
model_slugYesSlug of the target deAPI model the enhanced prompt will be used with (e.g., 'Flux1schnell'). The booster picks a guide that matches this model + type.
negative_promptNoOptional negative prompt to enhance alongside the main prompt.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the operation is synchronous, returns enhanced prompt(s) directly, and is charged per call, with a quote alternative. It does not cover error behavior, latency, or auth, but the key cost and sync traits are disclosed.

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

Conciseness5/5

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

Two short, front-loaded sentences with no wasted words. The purpose comes first, followed by the synchronous and cost behavior.

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?

An output schema exists and the input schema is fully documented, so the description does not need to restate return values or parameter details. It adequately covers the paid synchronous operation and points to the quote sibling, though it could mention required image cases for edits and animations had the schema not covered them.

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 all five parameters in detail. The description adds only a high-level reminder that the guide matches the model and inference type, which is largely already present in the model_slug schema text.

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

Purpose5/5

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

The description uses a specific verb and resource: 'Enhance a prompt using AI guides tailored to a specific deAPI model + inference type.' It explicitly frames the output as an enhanced prompt and distinguishes the tool from prompt_booster_price by pointing to the quote sibling.

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?

The description gives clear guidance to use prompt_booster_price first for a quote before incurring a charge. It establishes the synchronous paid context but does not state when not to use the booster or any prerequisites beyond the schema.

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