codebase-memory-mcp

Overview Schema Source Related Servers Discussions Admin

detect_changes

Read-onlyIdempotent

Maps a Git diff to changed files, callers, dependencies, and test impact so you can review code changes and assess risk.

Instructions

Map a Git diff to files and impact. Page with snapshot cursors.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`via`	No	Add via_qn, via_edge.
`depth`	No
`limit`	No
`scope`	No		impact
`seeds`	No	List changed-symbol seeds with independent pagination.	none
`since`	No
`format`	No		tree
`project`	Yes
`fixpoint`	No	Walk to closure; no depth.
`direction`	No	inbound=callers; outbound=dependencies; both=union.	inbound
`edge_types`	No	Inbound walk; default CALLS.
`seed_limit`	No
`base_branch`	No	Default: origin/HEAD, else main, else master, else the upstream.
`config_path`	No	Project config override; absolute or project-relative.
`seed_cursor`	No	Continue seeds:list; excludes nonzero seed_offset.
`seed_filter`	No	Product excludes indexed test metadata and configured test globs.	all
`seed_offset`	No
`module_limit`	No
`changed_limit`	No
`impact_cursor`	No
`impact_offset`	No
`module_cursor`	No
`module_offset`	No
`changed_cursor`	No
`changed_offset`	No
`max_output_tokens`	No	Sizing hint; hard ceiling is 4 UTF-8 bytes/token.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv0.12.1Oct 17, 2026

removedInput schema / properties / base_branch / default
```
Removed value: -"main"
```

addedInput schema / properties / base_branch / description

Added value: +"Default: origin/HEAD, else main, else master, else the upstream."

addedInput schema / properties / config_path

Added value: +{
+  "description": "Project config override; absolute or project-relative.",
+  "type": "string"
+}

addedInput schema / properties / edge_types

Added value: +{
+  "description": "Inbound walk; default CALLS.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / fixpoint

Added value: +{
+  "description": "Walk to closure; no depth.",
+  "type": "boolean"
+}

changedInput schema / properties / scope / enum

Previous value: -[
-  "files",
-  "impact"
-]New value: +[
+  "files",
+  "impact",
+  "tests"
+]

addedInput schema / properties / seed_cursor

Added value: +{
+  "description": "Continue seeds:list; excludes nonzero seed_offset.",
+  "type": "string"
+}

addedInput schema / properties / seed_filter

Added value: +{
+  "default": "all",
+  "description": "Product excludes indexed test metadata and configured test globs.",
+  "enum": [
+    "all",
+    "product"
+  ],
+  "type": "string"
+}

addedInput schema / properties / seed_limit

Added value: +{
+  "default": 50,
+  "maximum": 1000,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / seed_offset

Added value: +{
+  "default": 0,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / seeds

Added value: +{
+  "default": "none",
+  "description": "List changed-symbol seeds with independent pagination.",
+  "enum": [
+    "none",
+    "list"
+  ],
+  "type": "string"
+}

addedInput schema / properties / via

Added value: +{
+  "description": "Add via_qn, via_edge.",
+  "type": "boolean"
+}

Changed15 schema fields changedv0.11.0Sep 16, 2026

addedInput schema / properties / changed_cursor
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / changed_limit

Added value: +{
+  "default": 20,
+  "maximum": 5000,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / changed_offset

Added value: +{
+  "default": 0,
+  "minimum": 0,
+  "type": "integer"
+}

removedInput schema / properties / depth / description

Removed value: -"Max traversal hops from the changed symbols."

changedInput schema / properties / direction / description

Previous value: -"inbound (default) = the blast radius: transitive CALLERS of the changed symbols. outbound = what the changed code depends on. both = union."New value: +"inbound=callers; outbound=dependencies; both=union."

addedInput schema / properties / impact_cursor
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / impact_offset

Added value: +{
+  "default": 0,
+  "minimum": 0,
+  "type": "integer"
+}

removedInput schema / properties / limit / description

Removed value: -"Per-symbol impacted rows shown (nearest hops first). impacted_total is always exact and the impacted_modules rollup always complete regardless."

addedInput schema / properties / max_output_tokens

Added value: +{
+  "default": 3200,
+  "description": "Sizing hint; hard ceiling is 4 UTF-8 bytes/token.",
+  "maximum": 1000000,
+  "minimum": 128,
+  "type": "integer"
+}

addedInput schema / properties / module_cursor
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / module_limit

Added value: +{
+  "default": 20,
+  "maximum": 256,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / module_offset

Added value: +{
+  "default": 0,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / scope / default
```
Added value: +"impact"
```

removedInput schema / properties / scope / description

Removed value: -"files: changed files only (no traversal). impact (default): files + the transitive impact set."

removedInput schema / properties / since / description

Removed value: -"Git ref or tag to compare from (e.g. HEAD~5, v0.5.0). Diffs <ref>...HEAD."

Changed1 schema field changedv0.10.4Aug 14, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null

Addedv0.10.0Aug 10, 2026
Removedv0.9.0Jul 8, 2026
First observedv1.0.0Jun 9, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so safety is covered. The description's only behavioral disclosure is 'Page with snapshot cursors', which is a useful but vague hint about the pagination model; it says nothing about the multiple walk modes (depth vs fixpoint), base-branch resolution, or config overrides that dominate this tool's behavior.

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?

Two tightly written, front-loaded sentences with no padding. However, for a 26-parameter tool the brevity crosses into under-specification rather than true conciseness.

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?

No output schema and no annotation gaps to lean on; the description omits the multi-dimensional pagination model, the base-branch defaults, and the scope/direction modes. For a tool this complex it is not remotely complete.

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

Parameters1/5

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

With 26 parameters and only 38% schema description coverage, the description must carry significant param meaning, yet it clarifies none. It only loosely gestures at 'files and impact' (scope) and cursors, leaving depth, fixpoint, seeds, edge_types, direction, and the many offset/limit knobs undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Map a Git diff to files and impact'), which is concrete and understandable. It does not differentiate this from plausible siblings like compare_graphs or query_graph, and 'Page with snapshot cursors' is jargon that adds little clarity.

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?

No when-to-use guidance, no prerequisites, and no pointer to an alternative tool. An agent cannot tell from the description whether to reach for this versus compare_graphs or search_graph when analyzing changes.

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

Deploy Server

detect_changes

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools