Skip to main content
Glama
DeusData

codebase-memory-mcp

by DeusData
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

detect_changes

Read-onlyIdempotent

Detect changed code from a Git diff, mapping each change to affected files and impact. Page through results with snapshot cursors.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNo
limitNo
scopeNoimpact
sinceNo
formatNotree
projectYes
directionNoinbound=callers; outbound=dependencies; both=union.inbound
base_branchNomain
module_limitNo
changed_limitNo
impact_cursorNo
impact_offsetNo
module_cursorNo
module_offsetNo
changed_cursorNo
changed_offsetNo
max_output_tokensNoSizing hint; hard ceiling is 4 UTF-8 bytes/token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv0.11.0
    • 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."
  2. Changed1 schema field changedv0.10.4
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  3. Addedv0.10.0
  4. Removedv0.9.0
  5. First observedv1.0.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already establish that the tool is read-only, idempotent, and non-destructive. The description adds the behavioral detail of pagination via 'snapshot cursors,' which is beyond the annotations. However, it does not explain what a snapshot cursor is, how pagination behaves, or any other operational traits like output size limits or error conditions.

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?

The description is very short, with only two sentences, and the main purpose is front-loaded. Each sentence contributes information: the first states the primary purpose, the second notes pagination behavior. There is no redundancy or filler, though the brevity veers toward under-specification rather than tight, informative conciseness.

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

Completeness1/5

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

This is a complex tool with 17 parameters, minimal schema descriptions, no output schema, and no usage guidance. The description does not explain how the Git diff is determined, what 'impact' means, what the output contains, or how the pagination cursor system works. An agent cannot reliably call this tool correctly based on the provided description alone.

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?

With schema description coverage at only 12% and 17 parameters, the description must compensate, but it only hints that cursor-related parameters support pagination via 'Page with snapshot cursors.' It does not explain key parameters like scope, direction, base_branch, since, limit, depth, or the various offsets and cursors. Most parameters remain semantically opaque, so the description adds minimal value beyond the schema.

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?

The description states a clear action and resource: 'Map a Git diff to files and impact.' This is specific enough to distinguish the tool from siblings like compare_graphs or trace_path, which do not focus on Git diffs. However, 'impact' is somewhat vague and not explained, so it falls short of a 5.

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 its siblings such as compare_graphs, trace_path, or get_architecture. There are no conditional use cases, exclusions, or alternative tool mentions. The only hint is the purpose, which implies usage but does not explicitly state it.

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