Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Audit agent instruction consistency

audit_agent_instructions
Read-onlyIdempotent

Review caller-supplied instruction documents for duplicates, conflicting constraints, and risky bypass wording without executing or promoting them.

Instructions

Review bounded caller-supplied instruction documents for duplicates, possible opposing action constraints and risky bypass wording. No instruction is executed or promoted.

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": {
      "instructions": "<instructions>"
    },
    "name": "audit_agent_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
instructionsYes

Output Schema

NameRequiredDescriptionDefault
statusYes
warningYes
findingsYes
truncatedYes
sources_reviewedYes
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 establish read-only, idempotent, non-destructive, closed-world behavior. The description adds the important behavioral fact that instructions are neither executed nor promoted and specifies the review dimensions, though it does not discuss reporting depth or limits.

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 no filler. The second sentence adds a distinct and important safety constraint.

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?

Purpose and safety are clear, and the output schema handles return values while annotations cover safety. However, usage guidance and parameter semantics are thin, and with 0% schema description coverage those gaps matter for correct invocation.

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?

There is one array parameter whose item schema has source_id, priority, and text with 0% property-description coverage. The description says "bounded caller-supplied instruction documents" but does not explain the fields, priority enum, source_id format, maxItems, or text limits, so it does not compensate for the schema gap.

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 states a specific verb ("Review") and resource ("bounded caller-supplied instruction documents") and enumerates what is checked: duplicates, opposing action constraints, and risky bypass wording. It is clearly distinct from sibling audit tools, though it does not explicitly name an alternative.

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?

It implies the tool is for reviewing supplied instruction documents and notes they are bounded, but it does not state when to choose this over sibling audit tools or list prerequisites/exclusions. The safety note "No instruction is executed or promoted" is not usage guidance.

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