Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Review supplied code changes

review_code_change
Read-onlyIdempotent

Analyze a bounded unified diff for line-anchored risk signals, changed-file coverage, and review follow-ups to guide heuristic code-review triage.

Instructions

Analyze a bounded unified diff for line-anchored risk signals, changed-file coverage, and review follow-ups. Heuristics only: not a semantic review, vulnerability scanner or verified test result. Stateless, no repository access.

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": {
      "diff": "<diff>"
    },
    "name": "review_code_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
diffYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile needs no restating. The description adds genuinely new behavioral context: the analysis is heuristic-only, the tool is stateless and has no repository access, and the diff must be bounded – all of which shape how an agent should interpret and trust the result.

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?

Three short sentences, front-loaded with the action and outputs, then the trust caveat, then the operating constraints. No sentence is redundant and nothing is buried at the end.

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 full annotations and no output schema, the description covers input format, heuristic nature, statelessness, and the kinds of results returned. Only the size bound on the diff is left solely to the schema, which is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden and does add meaning: the single parameter must be a unified diff (not a raw file or commit reference) and must be bounded in size. It does not restate the concrete min/max length limits, but the format expectation is the more valuable semantic contribution and is delivered.

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?

The description names a specific verb and resource ("Analyze a bounded unified diff") and enumerates the outputs: line-anchored risk signals, changed-file coverage, and review follow-ups. It immediately rules out what it is not (semantic review, vulnerability scanner, verified test result), so an agent can distinguish it from any sibling without opening the 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 input condition is clear – supply a bounded unified diff when you want heuristic risk signals – and the exclusions ("not a semantic review, vulnerability scanner or verified test result") set expectations for when not to rely on it. It stops short of naming an alternative tool to use for deeper semantic or security review, so the routing guidance is implicit rather than explicit.

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