Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getMaestroRunStatus

Retrieve Maestro run status for a project, list all runs from the latest execution, or inspect a specific run ID to check WAITING, READY, DONE, FAILED, or CANCELLED results.

Instructions

Get the status of Maestro run(s) for a project. Omit runId to list all runs of the latest execution. Statuses: WAITING, READY (running), DONE, FAILED, CANCELLED.

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>"
    },
    "name": "getMaestroRunStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdNoSpecific run ID to inspect
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It helpfully enumerates the possible status values and clarifies that READY means running, but it says nothing about polling expectations, terminal vs. non-terminal states, permissions, or what an omitted-runId response looks like structurally.

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?

Two short sentences, front-loaded with the core action, then the runId behavior, then the status vocabulary. Nothing is redundant and no sentence fails to earn its place.

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 read tool with no output schema, the description covers the action, the optional-parameter behavior, and the returned status vocabulary. The remaining ambiguity is minor — what "latest execution" refers to and whether multi-run responses are lists.

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, but the description adds real meaning by explaining the effect of omitting runId (list all runs of the latest execution) rather than just naming it. That semantic is not captured by the schema's "Specific run ID to inspect".

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 uses a specific verb and resource ("Get the status of Maestro run(s) for a project"), which is clearly distinct from result-fetching siblings like getMaestroRunResults. It does not explicitly name a sibling to contrast with, so it falls short of a 5.

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?

It gives one concrete usage rule — omit runId to list all runs of the latest execution — which tells the agent how to widen scope. However, it offers no guidance on when to prefer this over getMaestroRunResults, listMaestroRuns, or getAppAutomateRunStatus, so routing between siblings is left to inference.

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