Skip to main content
Glama
qa-toolkit-mcp

qa-toolkit-mcp

by darizae

qa_audit_case_references

Audit test files for candidate references to indexed case IDs, identify gaps or ambiguities, and report evidence limits without claiming tests pass.

Instructions

Locate candidate references to indexed case IDs; never claim tests pass.

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": {
      "plan_path": "<plan_path>",
      "tests_path": "<tests_path>"
    },
    "name": "qa_audit_case_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_pathYes
tests_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 behavioral burden, and it does disclose one genuinely useful trait: results are only 'candidate' references and must not be treated as proof that tests pass, which signals a non-authoritative, heuristic output. It says nothing about read-only status, what happens with missing or malformed files, or how results are reported.

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?

Two short clauses with no filler, and the scope statement is front-loaded before the caution. It is compact to the point of under-specification rather than verbose, so it scores well on structure while leaving the gaps noted elsewhere.

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?

For a tool with two required, entirely undocumented file-path parameters, no annotations, and no output schema, the description should say what the inputs are and what the caller receives back. It supplies neither, so an agent knows the tool's stance ('candidate' only) but not how to invoke it correctly.

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%, so the description needed to explain plan_path and tests_path and instead mentions neither. Only the parameter names themselves hint that a plan file and a tests file are compared, so the description adds essentially no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Locate candidate references to indexed case IDs" gives a verb (locate) and a resource (references to case IDs), so the general intent is graspable. But it never says what is being scanned (the plan and tests files implied by the parameters), and 'indexed case IDs' is unexplained jargon, so an agent cannot confidently tell what this produces versus qa_compile_indexed_cases.

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 use this tool, when not to, or which sibling to prefer. The clause "never claim tests pass" is a caveat about interpreting results, not usage guidance, so the agent is left to infer the workflow position entirely.

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