Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Plan requirement-traceable tests

build_test_matrix
Read-onlyIdempotent

Drafts bounded positive, negative, boundary, and regression test cases from a given specification, flagging unspecified expectations without claiming tests ran.

Instructions

Draft bounded positive, negative, boundary and regression test cases for supplied requirements. Reuses the requirements parser, reports unspecified expectations and never claims tests ran.

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": {
      "specification": "<specification>"
    },
    "name": "build_test_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_casesNo
specificationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered for free. The description adds genuinely new behavior: output is 'bounded', unspecified expectations are surfaced as reported gaps, and it 'never claims tests ran' — an important guard against mistaking the draft for execution. It does not describe the shape of the returned matrix, which keeps it from a 5.

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 dense sentences, front-loaded with the action and artifact. Every clause adds information — case types, reuse of the parser, gap reporting, and the no-execution disclaimer — 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?

The planning-vs-execution distinction and bounded output make the tool safe to call, and there is no output schema requiring return-value explanation. However, with zero schema description coverage on both params and no output schema, the missing parameter guidance leaves a real gap for an agent deciding how many cases to request.

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?

Both parameters have 0% schema description coverage, so the description carries the full burden and largely fails: 'bounded' only faintly gestures at max_cases (default 24, max 80), and neither the cap semantics nor the specification argument's constraints (10–16000 chars) are explained. An agent gets no help on how large to set max_cases or what 'supplied requirements' should look like.

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?

States a concrete verb and artifact: 'Draft ... test cases for supplied requirements', and enumerates the case classes (positive, negative, boundary, regression). It also signals requirement traceability, matching the title. It does not name a sibling (e.g. audit_requirements) to sharpen the boundary, so it stops short of a 5.

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?

Usage is only implied by 'for supplied requirements' and 'Reuses the requirements parser' — an agent can guess this runs after requirements exist. There is no explicit when-to-use, no when-not-to-use, and no routing to alternatives such as audit_requirements or review_work_evidence, despite close-sounding siblings.

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