Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

maestroCheatSheet

Retrieve a Maestro flow YAML syntax reference covering file structure, commands, selectors, and the TestingBot run workflow before writing or fixing Maestro flows.

Instructions

Get a Maestro flow YAML syntax reference: file structure, commands, selectors, and the TestingBot run workflow. Call this before writing or fixing Maestro flows.

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": "maestroCheatSheet"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does disclose the subject matter being returned and that it is a reference lookup rather than an action. However, it never states that the call is read-only and side-effect free, whether the content is static or version-dependent, or how large the response is — modest gaps for a zero-parameter documentation tool but still unstated.

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 sentences, both earning their place: the first names the resource and its contents, the second gives the trigger condition. The usage instruction is front-loaded at the end where it is easy to scan, and no wording is redundant.

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 static reference lookup with no inputs and no output schema, the description covers what an agent needs to decide to call it: what content it returns and when. The one remaining gap is that, absent an output schema, it does not indicate the shape of the returned reference (markdown prose vs. copyable YAML snippets), which mildly affects how the agent should consume the result.

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?

The tool takes no parameters at all, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. The description's enumeration of reference topics is a reasonable substitute for parameter meaning.

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 a Maestro flow YAML syntax reference' — and enumerates the content covered: file structure, commands, selectors, and the TestingBot run workflow. That makes it clearly distinct in kind from the sibling action tools (runMaestroTest, getMaestroRunStatus, etc.), though it never explicitly contrasts itself with them.

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?

Offers explicit when-to-use guidance: 'Call this before writing or fixing Maestro flows.' That covers the primary trigger conditions well. It stops short of stating when not to call it (e.g. 'not needed for reading run results') or naming sibling alternatives, so it is clear context rather than a full routing rule.

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