Skip to main content
Glama

Designed test case pack — Atom

Designed test case pack

designed_test_case_pack
Read-onlyIdempotent

Submits a test-case-pack manifest (declared requirements and cases, technique application, negative and error guessing, risk selection, coverage) and returns a deterministic TEST_CASE_PACK_SOUND / TEST_CASE_PACK_NOT_SOUND / INSUFFICIENT_EVIDENCE verdict across four sections, including computed traceability, expected-result coverage and duplicate-id checks, with per-check evidence. Audits the declared pack; it writes no test cases.

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": "designed_test_case_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
packNoTest-case pack being audited.
casesNoDeclared test cases: {id, requirement_ids, level, preconditions_declared, steps_declared, expected_result, expected_result_written_before_execution, covers_boundary, covers_negative}.
coverageNoCoverage and suite-hygiene evidence.
requirementsNoDeclared requirements: {id}.
risk_selectionNoRisk-selection evidence.
technique_applicationNoTechnique-application evidence.
negative_and_error_guessingNoNegative and error-guessing evidence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds substantial context beyond that: deterministic verdict values, four audit sections, computed traceability, expected-result coverage, duplicate-id checks, and per-check evidence. It also clarifies that no test cases are written.

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?

Two sentences, front-loaded with the action and return contract. The parenthetical list is dense but purposeful, and the final clause prevents a common misuse.

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

Completeness5/5

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

For a complex seven-parameter audit tool with nested objects and no output schema, the description supplies the missing return contract and audit scope. Combined with full schema coverage and annotations, an agent has enough to invoke it correctly.

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 description coverage is 100%, so the seven parameters are already documented. The description enumerates the manifest components (requirements, cases, technique application, negative/error guessing, risk selection, coverage), which helps frame the payload but adds little syntax or meaning beyond the schema.

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

Purpose5/5

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

The description uses a specific verb ('Submits') and resource ('test-case-pack manifest'), and explicitly scopes the tool as an audit that writes no test cases. It clearly distinguishes the operation from test-case creation even without sibling tools.

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

Usage Guidelines4/5

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

It indicates the tool is for auditing a declared pack and explicitly says it writes no test cases, giving a when-not boundary. It does not name alternative tools or describe prerequisites, but the use context is clear.

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.