Skip to main content
Glama

Audit requirements-to-test coverage

bpj_audit_test_traceability
Read-onlyIdempotent

Map test cases to acceptance requirements, identify uncovered requirements and unknown references.

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

Input Schema

NameRequiredDescriptionDefault
testsYes
requirementsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 openWorldHint=false, so the safety profile carries no burden. The description adds genuine value by naming the outputs, notably that dangling test references are reported as 'unknown references' rather than silently dropped. It does not disclose how malformed lines are handled or whether results include counts/percentages, which for a pure-analysis tool is a modest gap.

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?

A single front-loaded sentence with no filler; the verb and the two outputs come first. It is efficient, though the terseness is part of why format and usage details are missing.

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?

With two required, format-sensitive string inputs, no output schema, and no annotations explaining return shape, the description should do more: it should state the input line format and characterize the result (which requirements are uncovered, which test IDs are unknown). It hints at the outputs but leaves the caller to read the schema titles for input structure.

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?

The description says nothing about the two required inputs, while the reported schema description coverage is 0%. The schema's own titles do carry the critical format ('one test-id:req1,req2 per line', 'one per line'), so the definition is not unusable, but the description itself contributes no parsing semantics, delimiter rules, or behavior for IDs that appear in both directions.

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?

Uses a specific verb+resource pair ('Map test cases to acceptance requirements') and states the two analytical outputs (uncovered requirements, unknown references). It is clear what the tool does, but it never distinguishes itself from the similar 'bpj_preview_test_matrix' sibling, so an agent cannot tell which of the two to pick from the description alone.

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 purpose: an agent can infer it should call this when checking requirement coverage. There is no explicit when-to-use condition, no prerequisites (e.g. that both lists must already be collected), and no pointer to an alternative such as the test matrix preview tool.

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.