Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getAiFailureAnalysis

Read a test's AI failure analysis, including root cause, timeline, log evidence, suggested fixes, failure category, likely owner, and confidence. Read-only; requires account AI Analysis enabled.

Instructions

Read the AI failure analysis (TestingBot AI Insights) of a test: summary, root cause, timeline, log evidence, suggested fixes, failure category, likely owner and confidence. Read-only: never starts an analysis or sends data to the AI provider. Requires the account owner to have enabled AI Analysis.

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

Input Schema

NameRequiredDescriptionDefault
sessionIdYesSession ID (or numeric test ID) of the test.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it declares read-only behavior, states it never triggers an analysis or transmits data to the AI provider, and flags an account-level prerequisite. It does not say what happens when no analysis exists yet (error, empty, or pending state) or whether results can be stale, which is the remaining behavioral gap.

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, front-loaded with the resource and payload contents, then constraints. Every clause adds information with no padding or redundancy.

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?

With no output schema and no annotations, the description compensates by listing the fields returned and the safety/auth constraints. For a single-parameter read tool this is nearly complete; only the not-yet-analyzed behavior and error mode are unaddressed.

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?

Only one parameter with 100% schema coverage, where the schema already explains it accepts a session ID or a numeric test ID. The description adds only 'of a test' as scope, contributing essentially nothing beyond the structured field, so the 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 ('Read') and resource ('AI failure analysis / TestingBot AI Insights of a test') and enumerates the returned artifacts (summary, root cause, timeline, log evidence, suggested fixes, category, owner, confidence), so an agent knows exactly what it retrieves. The explicit 'never starts an analysis' clause also separates it from the analysis-triggering sibling without requiring schema inspection.

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 the key prerequisite ('Requires the account owner to have enabled AI Analysis') and implies the division of labor via 'never starts an analysis', which tells the agent this tool is for retrieving an existing analysis rather than producing one. It does not name the alternative tool that actually starts an analysis, so it stops short of full routing guidance.

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