Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Runs Tool

amount.runs

Retrieves up to 50 recent manager-owned runs, filters queued or running jobs, or shows a specific rule's history; use it to locate a forgotten run UUID.

Instructions

Read-only. The newest runs (at most 50, newest first) the manager started or owns, each shaped like amount.status. Use active=true for "what is running now", or rule (uuid from amount.rules) for one rule's history. Find a forgotten run uuid here.

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": "amount.runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleNoOnly the runs of this rule (uuid from amount.rules)
activeNoOnly queued or running runs. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations are empty, so the description carries the full burden and does well: it declares read-only, the scope restriction (runs the manager started or owns), and the 50-run cap with newest-first ordering. It omits any mention of what happens when more than 50 runs exist (no pagination/truncation advice) and says nothing about auth or rate limits.

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?

Dense, front-loaded, and free of filler: scope and cap first, then the two filtering modes, then the disambiguating use case. Every clause contributes information an agent would otherwise have to guess.

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 two-parameter, no-output-schema, unannotated listing tool this is close to complete: it covers scope, cap, ordering, filter semantics, and points at amount.status for the record shape. The only real gap is the absence of guidance on paging past the 50-run window.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by glossing active in operational terms ('what is running now') and by tracing `rule` back to a uuid from amount.rules. It never restates the default-false behavior, so it adds meaning without fully duplicating the schema.

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 ('the newest runs ... the manager started or owns') with explicit scope, ordering, and cap (at most 50, newest first). It also cross-links the output shape to amount.status, so the agent knows what a run looks like without another lookup.

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 concrete conditional guidance: active=true for 'what is running now', and `rule` for a single rule's history, plus a stated purpose ('find a forgotten run uuid here'). It stops short of naming when to prefer an alternative over this tool, so it is clear context without full exclusion rules.

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