Skip to main content
Glama

Prompt Booster Price

prompt_booster_price

Calculates the price of a prompt-booster call for a chosen deAPI model and inference type, so you can estimate cost before enhancing a prompt.

Instructions

Calculate the price for a prompt-booster call.

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

Input Schema

NameRequiredDescriptionDefault
typeYesInference type in v2 dot notation (e.g., 'images.generations').
imageNoOptional reference image (URL, data URI, or base64) — relevant for image-based types.
promptYesThe prompt to enhance.
model_slugYesSlug of the target deAPI model.
negative_promptNoOptional negative prompt.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, yet it says nothing about whether this is side-effect free, whether it consumes credits, what currency/unit the price is in, or whether a paid job is created. The word 'calculate' implies a read-only estimate but that is never confirmed.

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?

A single front-loaded sentence with no filler. It is efficient but so terse that the brevity comes at the cost of required context.

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?

An output schema exists and all parameters are described, which lowers the burden. Still, for a pricing tool with no annotations, the definition omits the pricing unit, whether cost depends on model_slug versus type, and the intended call ordering with prompt_booster.

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 100%, so the input schema already documents type, prompt, model_slug, image, and negative_prompt. The description adds nothing about how those inputs affect the price beyond what the schema states, so baseline 3 applies.

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 ('calculate') and resource ('price for a prompt-booster call'), so the agent knows it returns a cost estimate rather than executing the booster. It does not explicitly distinguish itself from the many sibling *_price tools, but the tool name carries that mapping.

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?

No when-to-use guidance is given: nothing says this should be called before prompt_booster, whether it is required for cost preview, or how it relates to the ~18 other price endpoints. The agent must infer usage from the name alone.

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