Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Review task completion evidence

review_work_evidence
Read-onlyIdempotent

Audits caller-supplied work contract evidence against changed paths, command receipts, success criteria, prohibited actions, and risk review; returns HOLD or REPORTED_READY_FOR_INDEPENDENT_REVIEW.

Instructions

Fail-closed audit of a create_work_contract result against supplied changed paths, command receipts, criteria, prohibited actions and risk review. Returns HOLD or REPORTED_READY_FOR_INDEPENDENT_REVIEW; never independently verifies caller-supplied evidence or authorizes completion, merge or deployment.

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": {
      "contract": "<contract>"
    },
    "name": "review_work_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
checksNo
contractYes
acceptanceNo
observationsNo
changed_filesNo
operations_performedNo
human_review_reportedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety is largely covered. The description nevertheless adds real value by disclosing that the check is fail-closed, that it returns HOLD or REPORTED_READY_FOR_INDEPENDENT_REVIEW, and that it never independently verifies caller-supplied evidence nor authorizes completion, merge or deployment – an important caveat that prevents over-trusting a positive verdict.

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 no filler: the first defines the audit and its inputs, the second defines the outputs and the hard limits on what a pass means. The most consequential constraint (never authorizes deployment) lands last for emphasis rather than being buried.

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?

There is no output schema and the input schema is deeply nested, yet the description compensates by naming the possible return values and the trust boundary. It is still thin on several nested fields (observations, human_review_reported) and on what evidence_excerpt or exit_code nulls signify, so it is strong but not complete for a schema this complex.

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 0% across 7 parameters, so the description has to carry meaning and only partially does. It alludes to changed paths, command receipts, criteria, prohibited actions and risk level, but says nothing about observations, operations_performed, human_review_reported, or the tool_output vs self_report source distinction, leaving several parameters unexplained in both schema and prose.

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?

Names a specific verb (audit/review) and its exact resource: a create_work_contract result checked against changed paths, command receipts, criteria, prohibited actions and risk review. It also states the two possible verdicts, so an agent can distinguish this gate tool from create_work_contract without opening either schema.

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?

The opening phrase 'audit of a create_work_contract result' makes the triggering context clear: call this after a contract exists and work has been performed. It does not state explicit when-not conditions or name an alternative route (e.g., a re-review or escalation path), so it falls short of a full 5.

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