Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Status Tool

amount.status

Poll a run started by a delivery, fetch, recall, or measurement action to get status, percent, files and bytes done/total, current file, message, and whether it has finished.

Instructions

Read-only. Progress of ONE run started by amount.deliver, amount.fetch, amount.recall or amount.measure: status (queued/scanning/uploading/done/failed/cancelled), finished, percent, files and bytes done/total, current_file, message and, for a finished measurement, usage. This is the way to poll long operations; repeat every few seconds until finished is true. Only runs the manager started or owns are visible.

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": {
      "run": "<run>"
    },
    "name": "amount.status"
  }
}

Input Schema

NameRequiredDescriptionDefault
runYesRun uuid returned by a starting tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden well: it declares read-only behavior, enumerates the exact status lifecycle (queued/scanning/uploading/done/failed/cancelled), and discloses an access restriction ('only runs the manager started or owns are visible'). It does not explain error behavior for an unknown or foreign run uuid, leaving one gap.

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?

Front-loads the read-only constraint, then the purpose, then the return fields, then the polling instruction. Dense and largely waste-free, though the inline field enumeration makes one long sentence that could be trimmed.

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?

No output schema exists, so the description compensates by listing the returned fields (status, finished, percent, files/bytes done/total, current_file, message, usage). It is complete enough to call and interpret correctly, with only failure-mode behavior left unspecified.

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% and the single `run` parameter is already documented as the uuid returned by a starting tool. The description reinforces the provenance of the id but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (read the progress status of ONE run) and explicitly ties it to the four starting tools (amount.deliver, amount.fetch, amount.recall, amount.measure), which distinguishes it from list-oriented siblings like amount.runs or amount.browse.

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?

Gives clear operational guidance: it is the way to poll long operations, and you should repeat every few seconds until `finished` is true. It lacks an explicit exclusion (e.g., when to use amount.runs or amount.browse instead), so it stops just short of full when/when-not coverage.

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