Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Job Models Tool

aimage.job.models

Change a job's text or image model before execution by providing its UUID and the new planner or image model.

Instructions

Switch the text and/or image model of a job before it executes.

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": {
      "uuid": "<uuid>"
    },
    "name": "aimage.job.models"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesJob uuid
text_modelNoNew planner model
image_modelNoNew image model

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

B3.4/5.0
Behavior3/5

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

The annotation readOnlyHint=false already signals a mutation, and the description usefully adds the constraint that the switch must happen pre-execution. However, it is silent on what happens on a job that has already started, whether the change is reversible, or whether either model argument may be omitted ('and/or' suggests at least one is needed but the schema only requires uuid).

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?

A single front-loaded sentence with zero filler; the timing constraint sits in the most prominent position. Nothing is redundant or buried.

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 mutating tool with three parameters and no output schema, the description leaves key agent questions unanswered: which model identifiers are legal (there are no enums on text_model/image_model), whether both must be supplied or one suffices, and what state the job must be in. The annotation covers only the read/write polarity, so the description needs to carry more weight than it does.

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 'Job uuid', 'New planner model' and 'New image model' are already documented in the schema. The description's 'text and/or image model' wording loosely reinforces that the two model parameters are independently optional, but adds no format, allowed-value, or default information beyond the schema.

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?

Names a specific verb ('Switch') and a specific resource ('the text and/or image model of a job'), so an agent knows exactly what the call accomplishes. It does not distinguish itself from the sibling 'aimage.models' (which presumably enumerates available models), so a small amount of differentiation is missing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'before it executes' gives a real timing precondition that implies when the tool applies, but the description never states what to do instead if the job has already run, nor does it point to any alternative tool. Usage is inferable rather than explicitly guided.

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