Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

analyzeTestFailure

Explains why a finished test failed by running TestingBot AI failure analysis on its secret-masked logs and waiting for the result; use getFailureLogs for raw logs.

Instructions

Explain why a test failed with TestingBot AI Insights. Starts an AI failure analysis of a finished test (or returns the existing one without extra cost) and waits for the result. The test's curated, secret-masked logs are sent to TestingBot's AI provider, so this requires the account owner to have enabled AI Analysis in Account Settings. Use getFailureLogs instead when you want the raw logs.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "analyzeTestFailure"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoRun a fresh analysis even when a current one exists (counts towards the account's AI limits).
sessionIdYesSession ID (or numeric test ID) of the test.
waitSecondsNoHow long to wait for the analysis to finish (default 90, 0 = return immediately).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses blocking behavior ('waits for the result'), idempotent reuse ('returns the existing one without extra cost'), a cost/rate constraint tied to the account's AI limits, and significant data egress (curated, secret-masked logs sent to TestingBot's AI provider). The account-level prerequisite is also surfaced. Only edge behavior on wait timeouts is left implicit.

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?

Three sentences, front-loaded with the purpose, then the reuse/cost model, then the prerequisite and the alternative. Every sentence carries distinct information with no repetition of the title or schema.

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 three-parameter tool with no output schema, the definition covers purpose, cost, prerequisites, data handling, and the alternative. The remaining gap is the return shape and what the caller gets if waitSeconds elapses before the analysis finishes, which matters for an agent deciding how to poll.

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%, so all three parameters are already documented, including force's cost implication and waitSeconds' default and 0 semantics. The description adds only the framing that a non-forced call reuses an existing analysis at no extra cost, which is a minor supplement. Baseline 3 is appropriate.

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?

The description opens with a specific verb and resource ('Explain why a test failed with TestingBot AI Insights') and clarifies that the tool both starts an analysis and returns an existing one. It explicitly distinguishes itself from the raw-log sibling, so an agent can pick correctly without opening either schema.

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

Usage Guidelines5/5

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

It names a concrete alternative and the condition that selects it ('Use getFailureLogs instead when you want the raw logs'), and it states the prerequisite that AI Analysis must be enabled in Account Settings. That covers both when to use this tool and when to route elsewhere.

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