Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Design adversarial and property test cases

design_adversarial_tests
Read-onlyIdempotent

Generate bounded adversarial test ideas—negative, boundary, metamorphic, property and trust-boundary cases—from caller-supplied field contracts. Produces ideas only; never runs or writes executable tests.

Instructions

Generate bounded negative, boundary, metamorphic, property and trust-boundary test ideas from explicit caller-supplied field contracts. Never runs or generates executable tests.

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": {
      "fields": "<fields>"
    },
    "name": "design_adversarial_tests"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYes
max_casesNo

Output Schema

NameRequiredDescriptionDefault
casesYes
issuesYes
statusYes
warningYes
truncatedYes
total_fieldsYes
tests_executedYes
independently_verifiedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

A3.5/5.0
Behavior4/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 safety is covered structurally. The description still adds real value by ruling out execution and code emission ("Never runs or generates executable tests") and by characterizing output as bounded "ideas" rather than artifacts, which prevents an agent from expecting runnable test files.

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, zero filler, with the generation scope front-loaded and the critical exclusion placed immediately after it. Nothing in the text is redundant with the name or 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?

An output schema exists, so return structure need not be explained, and the exclusion of execution is well covered. However, for a tool whose entire input is an undocumented nested field-contract array, the definition leaves the agent guessing how to populate fields and when to prefer this over build_test_matrix, which is a noticeable gap.

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 must carry parameter meaning and largely does not. It alludes to field contracts and to a bound, but never explains what the per-field properties (id, type, min/max, required, invariant, untrusted) mean for the generated cases, nor how max_cases (4-80) shapes output volume.

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 uses a specific verb ("Generate") plus a precisely scoped resource ("negative, boundary, metamorphic, property and trust-boundary test ideas") and names the input source ("explicit caller-supplied field contracts"). That is clear about what the tool produces, but it never contrasts itself with the sibling build_test_matrix, so the agent must infer the boundary between the two.

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: the phrase "from explicit caller-supplied field contracts" signals the precondition that the caller must already have field contracts in hand, and "bounded" hints at the max_cases cap. There is no explicit statement of when to choose this over build_test_matrix or when not to use it at all.

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