Skip to main content
Glama

Generate a TAP test report

bpj_release_tap_report
Read-onlyIdempotent

Encode test outcomes into a TAP version 13 plan, results and skip directives.

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_tap_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
testsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already establish that this is a safe, idempotent, closed-world read/transform with no destructive effects, so the description carries a lighter burden. It usefully pins the output format to TAP version 13 with plan, results, and skip directives, but says nothing about how malformed or partial input is handled, the 6000-character limit, or what the produced text looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler, and the format version and three output components are stated economically. It is arguably too compressed for a tool whose sole input's structure is undocumented, but nothing is redundant.

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

Completeness2/5

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

No output schema exists, so the description must cover both input expectations and the produced TAP text; it only gestures at the latter. With a JSON-string parameter of unknown shape and a size cap, an agent still cannot tell what to pass or how failures and skips are signaled in the input.

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?

There is a single required parameter with 0% schema description coverage — only the title 'Test results (JSON)' and a maxLength of 6000. The description does not describe the expected JSON shape, field names, or how per-test status maps to TAP ok/not-ok and skip directives, which is exactly the meaning the schema leaves out.

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 gives a specific verb ('Encode') and resource ('test outcomes into a TAP version 13 plan, results and skip directives'), which is far more informative than the title alone. It does not distinguish itself from the similar bpj_release_junit_xml formatter or explain its relationship to bpj_tap_target_check, so sibling differentiation is left to inference.

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 implied by the verb and the TAP target: an agent can infer this is used when TAP-formatted output is wanted. There is no explicit statement of when to prefer it over bpj_release_junit_xml or other format emitters, and no preconditions or exclusions are given.

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.