mcp-lab-agent

by Wesley-Gomes93

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Analisar falhas de testes

analyze_failures

Analyze test run output and extract structured failures to identify root causes and guide fixes.

Instructions

Recebe output de testes e extrai falhas estruturadas.

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": {
      "runOutput": "<runOutput>"
    },
    "name": "analyze_failures"
  }
}

Input Schema

Name	Required	Description	Default
`runOutput`	Yes	Output do teste (stdout/stderr).

Output Schema

Name	Required	Description	Default
`ok`	Yes
`summary`	Yes
`failures`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.1Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether the tool is read-only, what happens with invalid input, or what specific failure formats it supports. This is a meaningful gap for a tool that processes external test output.

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?

The description is a single, front-loaded sentence with no redundant wording. It clearly conveys the core purpose without any fluff or unnecessary detail.

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

Completeness3/5

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

For a simple one-parameter tool with an output schema, the description is minimally adequate but lacks usage context and side-effect clarity. It does not position the tool relative to sibling test-analysis tools, so an agent could confuse it with deeper analysis tools.

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 coverage is 100% and the single parameter 'runOutput' is self-explanatory as test stdout/stderr. The description adds no extra meaning beyond the schema, so a baseline score of 3 is appropriate.

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 clearly states the action: receive test output and extract structured failures. It distinguishes itself from root-cause analysis tools like 'por_que_falhou' by focusing on structured failure extraction, though it could be more explicit about the output structure.

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 explicit guidance is given on when to use this tool versus alternatives like 'por_que_falhou' or 'suggest_fix'. The phrase 'Recebe output de testes' implies usage after test execution, but there is no mention of when not to use it or what input format is expected.

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