Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Cancel Tool

amount.cancel

Stops a queued or running amount run cooperatively: the worker halts before its next file and drops the partial copy. Check run status afterward; completed transfers remain.

Instructions

Ask a queued or running run to stop. Cooperative: the worker stops before its next file and drops the partial copy, so check amount.status afterwards. Files already transferred stay transferred. A finished run is returned unchanged.

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

Input Schema

NameRequiredDescriptionDefault
runYesRun uuid from amount.runs or a starting tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only supply readOnlyHint=false, so the description carries the real burden and does so well: it discloses cooperative cancellation, the exact stopping point (before the next file), that partial copies are dropped, that completed transfers are retained, and that finished runs are no-ops. These are precisely the side-effect details an agent cannot infer elsewhere.

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?

Four short sentences, front-loaded with the action, followed by mechanism, aftermath, and edge case in order of decision relevance. No filler or restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter state-changing tool with no output schema, the description covers trigger conditions, cancellation semantics, partial-result handling, and the terminal no-op case, and points to amount.status for verification. Nothing an agent needs in order to call it correctly is missing.

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?

With one parameter at 100% schema description coverage, the schema already defines `run` as a uuid sourced from amount.runs. The description adds only the state constraint (queued or running), which is about run lifecycle rather than parameter format, so 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: 'Ask a queued or running run to stop,' and immediately names the affected entity plus its state qualifier (queued or running). An agent can distinguish this from status/browse/delete siblings without opening any schema.

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 conditions for use (only queued or running runs) and an explicit follow-up instruction to check amount.status, which implies the intended workflow. It also states the no-op case (a finished run is returned unchanged), effectively telling the agent when not to bother, but it does not name a distinct alternative tool for other cancellation needs.

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