Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Job Approve Tool

aimage.job.approve

Approve a planned job that exceeded its estimated cost approval threshold so the assigned worker can execute it.

Instructions

Approve a planned job whose estimated cost exceeded the approval threshold so the worker may execute it.

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

Input Schema

NameRequiredDescriptionDefault
uuidYesJob uuid

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?

Annotations only declare readOnlyHint=false, so the description must supply the mutation context; it does so by explaining the gating condition and that approval unlocks worker execution. It stops short of describing side effects such as whether approval is reversible, what error is returned if the job is not awaiting approval, or whether permission beyond the caller is required.

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 sentence, front-loaded with the action, containing the precondition and the outcome with no redundant wording. Every clause contributes information an agent would otherwise have to infer.

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 simple one-parameter mutation with no output schema, the description covers purpose and triggering condition adequately. It omits prerequisite job state and post-approval behavior, which matter for a workflow-gating action that sits alongside cancel and show operations.

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?

There is a single required parameter (uuid) and schema description coverage is 100%, so the schema already carries the parameter documentation burden. The description adds no format, sourcing, or constraint detail for the uuid beyond what the schema states, which is the expected baseline for a fully covered single-parameter tool.

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 gives a specific verb ('Approve') and resource ('a planned job'), plus the gating condition (estimated cost exceeded the approval threshold) and the resulting effect (the worker may execute it). It is clear what the tool does, though it does not explicitly distinguish itself from adjacent siblings like aimage.job.cancel or aimage.job.show.

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 clause 'whose estimated cost exceeded the approval threshold' implicitly tells the agent when approval is needed, which is useful contextual guidance. However, there is no explicit when-not guidance, no mention of the required job state, and no named alternative for inspecting or rejecting a job instead.

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