Skip to main content
Glama

data-api-code

junit_tap_test_report_parse

Parse JUnit XML or TAP (Test Anything Protocol) test result reports into structured pass/fail/skip counts and failing test trace 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": "junit_tap_test_report_parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose what the parser returns (counts plus failing test traces), which is genuine behavioral value. However, it says nothing about how the filePath source is read, precedence between inline text and a file, or how malformed/non-test XML is handled.

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?

A single front-loaded sentence with zero filler: verb first, both accepted formats named, and the parenthetical expansion of TAP adds clarity rather than noise.

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?

The description covers the result side well for a tool with no output schema, so return values need no further explanation. It is incomplete on the input side, since the two-parameter source selection and error behavior are undocumented in both the schema and the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters (text, filePath), and the description never mentions them. An agent cannot tell from either source whether the two inputs are alternatives, whether either is required, or what path format filePath expects.

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?

Names a specific verb (Parse) and resource (JUnit XML or TAP test result reports), and previews the output shape (pass/fail/skip counts and failing trace details). It is clearly distinguishable from the converter/analyzer siblings, though it does not explicitly contrast with any of them.

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

Usage Guidelines3/5

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

Usage is only implied by the input formats named: an agent holding a JUnit XML or TAP report infers this is the right tool. There is no explicit when-to-use statement, no prerequisite or exclusion, and no routing to a sibling for related tasks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources