Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Job Reply Tool

aimage.job.reply

Submit an answer to a planner's question or refine instructions for a waiting job by providing its UUID and your message.

Instructions

Answer the planner's question or refine the instruction of a job that is waiting on you.

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>",
      "message": "<message>"
    },
    "name": "aimage.job.reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesJob uuid
messageYesYour answer / refinement

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint=false annotation already tells the agent this is a mutating call, so the description's job is to explain the mutation. It hints that the reply unblocks or refines a waiting job, but does not say whether the job resumes automatically, whether the reply is recorded permanently, or whether repeated replies are allowed.

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?

One short sentence, front-loaded with the action and given meaning by the trailing state qualifier. No filler or redundant restatement of the schema.

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?

For a two-parameter, no-output-schema tool the definition is workable but thin: it never says what the return looks like, whether the job state changes, or how the message content is interpreted by the planner. Nothing is actively misleading, but the agent must guess at post-call effects.

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%, with both uuid and message documented in the schema itself, so baseline is 3. The description's 'planner's question' and 'refine the instruction' phrasing adds a little framing about what belongs in message but no format, length, or constraint details 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?

States a specific verb pair (answer / refine) and a specific resource (a job's planner question or instruction), and the qualifier 'waiting on you' scopes it to jobs in a blocked state. It implicitly differentiates from siblings like approve/cancel by being a free-text response rather than a decision, though it never names them.

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?

Usage is implied by the phrase 'a job that is waiting on you' — the agent can infer it should call this when a job has surfaced a question. There is no explicit when-not guidance, no mention of how this relates to approve/cancel, and no statement about what happens if the job is not actually waiting.

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