Skip to main content
Glama

Generate a JUnit XML report

bpj_release_junit_xml
Read-onlyIdempotent

Render test names, outcomes and durations into an escaped JUnit XML suite.

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": {
      "tests": "<tests>"
    },
    "name": "bpj_release_junit_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
testsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds the useful detail that output is XML-escaped, but says nothing about output shape, size limits, or how invalid input 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?

One sentence, front-loaded with the action and the artifact, with no filler or repetition of the title.

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 one-parameter, non-destructive rendering tool with annotations covering safety, the description is close to sufficient. The gap is that the required JSON contract for 'tests' and the returned value are never described, leaving the most error-prone part of invocation unspecified.

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 0% and the single parameter 'tests' only has a title and a 6000-character maxLength. The description partially compensates by indicating the input should contain names, outcomes, and durations, but it does not give the JSON field names or structure an agent would need to build a valid payload.

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 concrete verb (render) and a concrete artifact (escaped JUnit XML suite) and specifies the payload contents (test names, outcomes, durations). This distinguishes it from reporting siblings such as bpj_release_tap_report, though it does not name that alternative explicitly.

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 statement of when to choose this over a TAP or other report format, no prerequisites, and no exclusions. The intended use is only implied by the tool name and the word 'JUnit'.

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.