mcp-code-shrinker

Validate Multi-file Patch

patchset.validate

Validate an entire patch set in one sandbox to verify correctness and compatibility.

Instructions

Validate the whole patch set in one sandbox.

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": {
      "patchsetId": "<patchsetId>"
    },
    "name": "patchset.validate"
  }
}

Input Schema

Name	Required	Description	Default
`patchsetId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Jul 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The description does not disclose behavioral traits beyond the annotations. It says 'Validate' but does not clarify if it modifies state, returns results, or has side effects. Given readOnlyHint=false and destructiveHint=false, additional context about whether validation is a safe read operation would help.

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

Conciseness3/5

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

The description is a single sentence, which is concise, but it is too minimal. It could include more information without being verbose.

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

Completeness2/5

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

Given the simplicity of the tool (1 param, no output schema), the description fails to provide enough context for an agent to use it effectively. Missing details include what validation entails, return format, and how to get the patchsetId.

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?

The single parameter 'patchsetId' is a string with no description in the schema (0% coverage). The description does not explain what a patchsetId is, how to obtain it, or its format. The title implies it's a patch set identifier, but that is insufficient.

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 clearly states the action 'Validate' and the resource 'the whole patch set in one sandbox'. It distinguishes this tool from siblings like patch.validate (singular patch) and other patchset actions (propose, apply, rollback).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like patch.validate. It does not mention prerequisites, context, or exclusions.

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