Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Audit software requirements

audit_requirements
Read-onlyIdempotent

Inspect requirement text for missing acceptance scenarios, vague obligations, and duplicates, returning line-linked clarification prompts to resolve gaps. It does not validate business correctness.

Instructions

Inspect bounded requirement text for missing acceptance scenarios, qualitative obligations and duplicates. Returns source-line-linked clarification prompts; cannot validate business correctness.

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

Input Schema

NameRequiredDescriptionDefault
specificationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds context the annotations cannot: the input must be bounded text, the return value is source-line-linked clarification prompts, and the tool deliberately stops short of judging business correctness. The remaining gap is that the size/truncation behavior implied by "bounded" is not spelled out.

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 tight sentences with zero filler: the first front-loads what is inspected and the specific checks, the second covers the return shape and the scope limit. Every clause carries information an agent needs.

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

Completeness4/5

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

For a one-parameter tool with no output schema, the description does the important work: it characterizes both input (bounded text) and output (source-line-linked clarification prompts) and states a limitation. Missing is any note on size limits or what happens with oversized input, given the maxLength constraint.

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?

There is a single parameter with 0% schema description coverage, so the description must carry the meaning. "Bounded requirement text" tells the agent the content type and hints at length limits (the schema caps at 16000 chars), which is useful, but no format, granularity, or example of what constitutes one requirement unit is given.

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 specific verb ("Inspect") and a specific resource ("bounded requirement text") plus the concrete checks performed: missing acceptance scenarios, qualitative obligations, and duplicates. It does not name any sibling tool or explain how it differs from reviewers like review_code_change or assess_release_readiness, so it is clear but not differentiating.

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 implied by the phrase "bounded requirement text" and sharpened by the exclusion "cannot validate business correctness," which tells the agent one thing this tool is not for. However, there is no explicit trigger condition, no statement of when to prefer it over a sibling review tool, and no prerequisite guidance.

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