RepoPilot

Verify a dependency change after local work

verify_dependency_change

Read-onlyIdempotent

CALL after changing the manifest/lockfile and running local checks. Compares the exact evaluated target with the resolved result and caller-reported proof receipts, checks every version in resolved_changes for advisories (list all packages the lockfile change added or changed), reports missing/failed evidence and residual risk, and labels receipts as caller asserted. It never runs commands or stores diff/check output.

Input Schema

TableJSON Schema

Name	Required	Description
`diff`	No
`after`	Yes
`checks`	Yes
`evaluation`	Yes	The verification_context object exactly as evaluate_dependency_change returned it, passed back unchanged. Its signature covers every field, so edit nothing inside it. Sending the whole evaluate result instead is accepted; the receipt is read out of its verification_context.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tool`	Yes
`agent`	Yes
`status`	Yes
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026
- changedInput schema / properties / after / properties / resolved_changes / maxItems
```
Previous value: -100New value: +1000
```

Changed2 schema fields changedSep 30, 2026

changedInput schema / properties / after / properties / dependency_usage / description

Previous value: -"Optional local call shapes for this dependency under native Node with default conditions. No source, paths, local names or call arguments. Coverage is always partial; transpiled/bundled code is unsupported."New value: +"Optional local call shapes for this dependency under native Node with default conditions. No source, paths, local names or call arguments. Coverage is always partial; transpiled CommonJS output is read, bundles are unsupported. instance_member names a method called on an instance of the export."

addedInput schema / properties / after / properties / dependency_usage / properties / uses / items / properties / instance_member
```
Added value: +{
+  "maxLength": 100,
+  "pattern": "^[A-Za-z_$][A-Za-z0-9_$]*$",
+  "type": "string"
+}
```

Changed1 schema field changedSep 24, 2026

addedInput schema / properties / after / properties / dependency_usage

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional local call shapes for this dependency under native Node with default conditions. No source, paths, local names or call arguments. Coverage is always partial; transpiled/bundled code is unsupported.",
+  "properties": {
+    "coverage": {
+      "const": "partial",
+      "type": "string"
+    },
+    "runtime": {
+      "additionalProperties": false,
+      "properties": {
+        "arch": {
+          "maxLength": 32,
+          "pattern": "^[a-z0-9_]+$",
+          "type": "string"
+        },
+        "node": {
+          "maxLength": 32,
+          "pattern": "^[0-9]+\\.[0-9]+\\.[0-9]+$",
+          "type": "string"
+        },
+        "platform": {
+          "maxLength": 32,
+          "pattern": "^[a-z0-9_]+$",
+          "type": "string"
+        }
+      },
+      "required": [
+        "node",
+        "platform",
+        "arch"
+      ],
+      "type": "object"
+    },
+    "schema_version": {
+      "const": 1,
+      "type": "integer"
+    },
+    "uses": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "export_path": {
+            "items": {
+              "maxLength": 100,
+              "pattern": "^[A-Za-z_$][A-Za-z0-9_$]*$",
+              "type": "string"
+            },
+            "maxItems": 2,
+            "type": "array"
+          },
+          "loader": {
+            "enum": [
+              "require",
+              "import"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "loader",
+          "export_path"
+        ],
+        "type": "object"
+      },
+      "maxItems": 50,
+      "type": "array"
+    }
+  },
+  "required": [
+    "schema_version",
+    "runtime",
+    "coverage",
+    "uses"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 31, 2026

addedInput schema / properties / evaluation / description

Added value: +"The verification_context object exactly as evaluate_dependency_change returned it, passed back unchanged. Its signature covers every field, so edit nothing inside it. Sending the whole evaluate result instead is accepted; the receipt is read out of its verification_context."

Changed1 schema field changedAug 17, 2026

addedInput schema / properties / evaluation / properties / baseline_project_snapshot

Added value: +{
+  "const": "not_supplied",
+  "description": "Present only when the evaluation was made without a project snapshot. Part of the signed identity — pass it back verbatim.",
+  "type": "string"
+}

AddedAug 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds genuinely new behavioral facts: it never executes commands, never stores diff/check output, and it labels receipts as caller-asserted rather than verified — important trust semantics not captured by annotations.

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?

Two dense sentences, front-loaded with the imperative CALL trigger, and every clause adds information about behavior or inputs. It is long but not padded, though it could be broken into shorter sentences for scanability.

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 complex verification tool with an output schema present (so return format need not be explained), the description covers sequencing, comparison behavior, advisory scanning, evidence-gap reporting, and non-execution. It is nearly complete, with only parameter-level detail for the nested inputs left thin.

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 only 25%, so the description must compensate, and it does explain a few fields (resolved_changes as packages added/changed, receipts as caller-reported). However most of the large nested schema (after, checks, evaluation) gets no semantic elaboration in the description, leaving real gaps.

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 states concrete verbs and resources: it compares the evaluated target against the resolved result and caller receipts, checks advisories across resolved_changes, and reports missing/failed evidence and residual risk. An agent can distinguish this from evaluate_dependency_change, which produces the evaluation this tool consumes.

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?

It gives an explicit trigger ('CALL after changing the manifest/lockfile and running local checks'), which is exactly the when-to-use guidance an agent needs. It does not name when-not-to-call or point at a sibling alternative, so it falls short of a 5.

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

All RepoPilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?