Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Estimate Tool

aimage.estimate

Estimate the cost of image, chat, transcription, or speech jobs with a chosen model and controls before queuing to confirm budget.

Instructions

Estimate the cost of a number of images (or chat/transcription/speech) with a given model and controls before queuing a job.

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": {
      "model": "<model>"
    },
    "name": "aimage.estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoe.g. 1024x1024
countNoNumber of images (default 1)
modelYesModel id from aimage.models
actionNoimage (default), upscale, chat, transcribe or speak
qualityNoe.g. low, medium, high
backgroundNoe.g. transparent
aspect_ratioNoe.g. 16:9

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

A3.6/5.0
Behavior3/5

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

With an empty annotations object, the description carries the full disclosure burden. It does convey the most important behavioral trait — that this is a non-committal estimate made "before queuing a job" — but says nothing about whether the call consumes credits, whether an authenticated account is required, or what the estimate response contains.

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; the core purpose lands in the first few words. The parenthetical listing of non-image actions is slightly clunky but does real work by widening the tool's apparent scope.

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 7-parameter tool with full schema coverage and no annotations, the description is sufficient to select and call it correctly. The only real gap is that, with no output schema, it does not characterize the returned estimate beyond the word "cost".

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 every parameter is already documented in the input schema, including the action values and examples for size/quality. The description only restates the model and count dimensions and adds no syntax, default, or interaction rules (e.g. how count interacts with size for pricing).

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 pairs a specific verb ("Estimate") with a specific resource ("the cost of a number of images ... with a given model") and clarifies the scope beyond images by naming chat/transcription/speech. The phrase "before queuing a job" implicitly separates it from the job-creation siblings, though it never names a specific alternative tool.

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 gives a clear usage context: run this as a pre-flight check before committing to a job. It does not state any exclusion or name the alternative to use once you have already decided to queue, so the guidance is clear but not fully comparative.

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