Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Models Tool

aimage.models

Lists available text, image, voice, and speech models with prices so you can choose the right model for a job.

Instructions

List the text, image, voice and speech models the gateway offers, with prices. Pick text_model / image_model for jobs from here.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "aimage.models"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoBypass the cached catalogue

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?

No annotations are supplied, so the description must carry the behavioral burden. It discloses that results include prices and is evidently a read operation, but it says nothing about caching (that only appears in the schema), ordering, result size, or whether the catalogue is account-scoped. The refresh parameter's cached-versus-live behavior is never mentioned in the description itself.

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 sentences, no filler, with the enumeration of model types front-loaded. The second sentence is compact but slightly ambiguous ("from here", "jobs" – the caller must infer these are the aimage.job.create fields), costing a point.

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?

There is no output schema, so the description is the only source for return value information; it covers the important part (models plus prices) but not the shape (identifier fields, currency/unit of price, ordering). For a simple one-parameter list tool this is adequate but leaves the agent guessing at field names it is told to reuse.

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% and the single optional parameter `refresh` is already documented as "Bypass the cached catalogue". The description adds no meaning beyond that – no indication of when a refresh is worth incurring, or staleness characteristics – so the baseline 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?

"List the text, image, voice and speech models the gateway offers, with prices" gives a specific verb (List) and resource (gateway model catalogue) plus the categories covered, so the agent knows exactly what the call returns. It does not, however, distinguish this catalogue from the similarly named sibling aimage.job.models, which an agent could reasonably confuse with it.

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?

"Pick text_model / image_model for jobs from here" supplies clear context: this is the lookup step before creating a job, and it names the fields to pull. There are no exclusions or conditions (e.g. when to call it versus aimage.estimate or aimage.job.models), so it is clear but not complete guidance.

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