Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

cancelMaestroRun

Cancels a running Maestro test run using its project ID and run ID, stopping execution when you no longer need it.

Instructions

Cancel a running Maestro run.

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": {
      "projectId": "<projectId>",
      "runId": "<runId>"
    },
    "name": "cancelMaestroRun"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID to cancel
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden for a mutation, but it does not. It does not say whether cancellation is graceful or immediate, whether it is idempotent, what happens if the run has already finished, or what errors occur for an invalid runId.

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?

A single front-loaded sentence with no filler, so it is concise in form. The brevity works against it, though, because the space saved is space that a destructive operation needs for caveats.

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

Completeness2/5

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

For a destructive, unannotated mutation with no output schema, the definition is too thin. It omits permission requirements, effects on any in-flight steps, and result semantics, leaving the agent to guess at the consequences of calling it.

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 description coverage is 100%: both projectId and runId are documented inline with clear meaning. The description adds nothing beyond the schema, which is acceptable at full coverage but is the baseline rather than an improvement.

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?

States a specific verb (cancel) and resource (Maestro run), which is enough to distinguish it from siblings such as retryMaestroRun or getMaestroRunStatus. However, it does not clarify the scope of what gets cancelled or how it relates to the run lifecycle.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool rather than retryMaestroRun, or when simply letting a run finish is preferable. It also does not tell the agent where to get a valid runId (for example, from listMaestroRuns).

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