Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Jobs Tool

aimage.jobs

Track processing by listing the acting manager's AIMage job batches with status and progress.

Instructions

List the acting manager's AIMage jobs (batches) with status and progress.

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.jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure; it signals a read-style collection operation and says each entry carries status and progress, which is useful. It does not say whether completed/failed jobs are included, whether results are paginated or ordered, or how many are returned by default.

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 naming the actor, the resource, and the payload contents, with zero redundant wording. Nothing needs trimming.

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 zero-param, un-annotated list tool with no output schema, the description covers what is listed, for whom, and that each item reports status and progress. Missing are ordering, volume, and whether finished jobs appear — minor gaps for a simple read operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline of 4 applies; the empty schema leaves nothing further for the description to explain. The parenthetical "(batches)" adds terminology clarification rather than parameter meaning.

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 acting manager's AIMage jobs (batches)" gives a specific verb and resource, and the plural "jobs" plus the "(batches)" gloss implicitly separates it from the singular aimage.job.show / job.cancel siblings. It stops short of naming any alternative explicitly, so it is clear but not fully differentiated.

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 scope "acting manager's" implies when it applies (you see your own jobs), but there is no statement of when to use this versus aimage.job.show or aimage.files, and no exclusions or prerequisites. Usage must be inferred from the sibling names rather than the definition.

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