Skip to main content
Glama
jigyasudham

veto

by jigyasudham
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

veto_diff_review

Read-only

Reviews a git diff by running code review, security scan, and secrets scan in parallel across changed files, then returns a pass/warn/fail verdict with per-file findings and a CI-ready summary.

Instructions

Reviews a git diff — runs code review, security scan, and secrets scan in parallel across all changed files. Returns a structured verdict (pass/warn/fail), per-file findings, and a CI-ready summary. Pass diff directly or let Veto read it from project_dir automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diffNoThe git diff to review. If omitted, Veto runs git diff HEAD in project_dir.
contextNoOptional: PR description, ticket number, or focus area.
project_dirNoAbsolute project path. Used to auto-read git diff if diff is not provided, and to inject codebase context.
agent_outputsNoPhase 2 responses from the host AI (JSON). Pass this back when prompted by the server to complete the agentic loop.
agent_responseNoPhase 2 response from the host AI (JSON). Pass this back when prompted by the server to complete the agentic loop.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.7.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, confirming no mutations. Description adds that scans run in parallel and returns a verdict. No contradictions. Somewhat lacking detail on output structure, but acceptable.

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-load the purpose, then output and input options. No filler. Efficient and well-structured.

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?

Covers main aspects: what it does, output, input options. Could specify default behavior when both diff and project_dir are omitted, but overall complete for a tool with good annotations.

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 100%, so the tool description adds minimal new meaning beyond what schema already provides. Baseline of 3 is appropriate.

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 it reviews a git diff, runs three scans in parallel, and returns a structured verdict. It distinguishes itself from sibling tools by combining code review, security scan, and secrets scan into one tool.

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

Usage Guidelines5/5

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

Explicitly tells when to use: for reviewing a git diff. Implies alternatives: individual scans for specific needs. Provides guidance on input: pass diff directly or auto-read from project_dir.

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

Deploy Server

Other Tools