Skip to main content
Glama
Sign In
QA Copilot AI

QA Copilot AI

by Sham-coder16
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

analyze_report

Analyze automation test reports to extract failure details for root cause analysis and effective debugging.

Instructions

Analyze automation test report and extract failure details

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It states what it does but does not disclose behavioral traits such as input source, return format, or whether it is a read-only operation. For an analysis tool, this is slightly below adequate.

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, concise sentence that is front-loaded with 'Analyze automation test report' followed by the specific action. Every word serves a purpose with no redundancy.

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?

Given the absence of parameters, annotations, and output schema, the description provides a minimal viable explanation. However, it leaves ambiguity about what 'extract failure details' entails and how the report is provided, making it merely adequate.

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 has zero parameters, and the baseline for this case is 4. The description adds no parameter details, but none are needed since the schema is empty and coverage is vacuous.

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 tool's purpose: 'Analyze automation test report and extract failure details' uses a specific verb and resource. It distinguishes from siblings by indicating a report-level analysis, though it doesn't explicitly differentiate from 'analyze_failure'.

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?

There is no guidance on when to use this tool versus alternatives. The description lacks any mention of prerequisites, exclusions, or recommended use cases relative to sibling tools like 'analyze_failure' or 'classify_failure'.

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

Deploy Server

Other Tools