Skip to main content
Glama

pre-merge-review

Pre-merge Review Pack — One unified diff in, one merge decision out: the PR exploit gatekeeper (bug hunter, patch synthesizer, secret/dependency/SAST scans) plus the adversarial Unicode / Trojan Source gate. Runs diff-gatekeeper ($0.50) + unicode-safety-gate ($0.25) in one paid call for 20% less than buying them separately. Charged only when every member succeeds.

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": "pre-merge-review"
  }
}

Input Schema

NameRequiredDescriptionDefault
diffYesUnified diff of the change (git diff / PR .diff).
contextNoWhat the PR is supposed to do.
packageJsonDiffNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well on economics: it discloses per-member prices, the 20% bundle discount, and the all-or-nothing billing rule ('charged only when every member succeeds'). It does not state whether the operation touches the repository (read-only vs mutating) or what the returned 'merge decision' contains, which are the remaining behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the value proposition and the input/output contract, then the composition, then pricing. Dense but every clause carries information; the pricing detail is slightly promotional yet material to a paid tool, so it earns its place.

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 composite paid tool with no output schema, the description covers composition, cost, and failure billing, which is the key decision-relevant context. It leaves the result payload shape and the undocumented third parameter unexplained, so it is strong rather than complete.

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 coverage is 67%, so two of three parameters are documented in the schema, but packageJsonDiff has no description in either place and the description never mentions it, nor does it explain the optional 'context' hint. The phrase 'one unified diff in' mildly understates the three-parameter surface. Description adds essentially nothing beyond the schema.

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 input and output ('One unified diff in, one merge decision out') and enumerates the composed members (diff-gatekeeper plus unicode-safety-gate, with bug hunter, patch synthesizer, secret/dependency/SAST scans). An agent can distinguish this bundle from either constituent gate without opening a 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 bundling rationale ('one paid call for 20% less than buying them separately') makes clear this is the combined path when both gates are wanted, and names the two siblings explicitly. It stops short of stating when to prefer the individual gates instead — e.g. when only Unicode scanning is needed — but the context for choosing this over alternatives is discernible.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources