ShadowGit MCP Server

Write a range's Lens words

write_lens_words

DestructiveIdempotent

Writes the user-facing summary, step titles, bodies, why notes, excerpts, and card roles for a ShadowGit Lens range using IDs returned by get_lens.

Instructions

Write the words the user reads in ShadowGit's Lens for a range get_lens read: a summary, each step's title and body, with a why and an excerpt, each card's role, by the ids get_lens gave. An older ShadowGit takes plain text alone; text past its limit is cut; unknown ids are left out. The app keeps the words in its history: a card's role shows in any later range while its code is unchanged. When the session changed areas whose docs pages need words, the answer's next names them, the session's last step: get_docs, then write_docs.

Input Schema

Name	Required	Description
`base`	Yes	The base get_lens answered (null: from the start of the history)
`head`	Yes	The head get_lens answered
`repo`	No	Project name or absolute path. Defaults to the current project.
`flows`	No	Per flow: a verb phrase, e.g. "draws a range"
`steps`	No	Per step: a title naming what it does, and its words; a step's entry replaces everything written for that step before, so send its title, body, why and excerpt together
`layers`	No	Per layer: a short name, where the default does not say where code runs
`summary`	No	What the change does and why, in two sentences
`components`	No	Per changed card: the role it plays, in a few words

Output Schema

Name	Required	Description
`next`	No	The step that follows: the docs pages the session changed
`repo`	Yes
`applied`	Yes
`ignored`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.6.1Oct 29, 2026

addedOutput schema / properties / next

Added value: +{
+  "description": "The step that follows: the docs pages the session changed",
+  "type": "string"
+}

Changed6 schema fields changedv2.2.0Oct 19, 2026

changedInput schema / properties / steps / description

Previous value: -"Per step: a title naming what it does, and one or two sentences"New value: +"Per step: a title naming what it does, and its words; a step's entry replaces everything written for that step before, so send its title, body, why and excerpt together"

addedInput schema / properties / steps / items / properties / body / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "properties": {
+        "card": {
+          "type": "string"
+        },
+        "text": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "text"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+]

addedInput schema / properties / steps / items / properties / body / description

Added value: +"One or two sentences: plain text, or pieces, where a piece with a card links that card of the step by its id, only where the text names it"

removedInput schema / properties / steps / items / properties / body / type
```
Removed value: -"string"
```

addedInput schema / properties / steps / items / properties / excerpt

Added value: +{
+  "description": "At most 12 lines that changed, of one of the step's symbols as get_lens lists them: its path on that side, its name, the side and the lines",
+  "properties": {
+    "lines": {
+      "properties": {
+        "end": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "start": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "start",
+        "end"
+      ],
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "path": {
+      "type": "string"
+    },
+    "side": {
+      "enum": [
+        "base",
+        "head"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "path",
+    "name",
+    "side",
+    "lines"
+  ],
+  "type": "object"
+}

addedInput schema / properties / steps / items / properties / why

Added value: +{
+  "description": "Why, in the author's own words: one of get_lens's quotes, or part of one, word for word, within the why limit (a longer quote is left out, not cut); left out where none says why",
+  "properties": {
+    "quote": {
+      "type": "string"
+    },
+    "source": {
+      "const": "commit",
+      "type": "string"
+    }
+  },
+  "required": [
+    "quote",
+    "source"
+  ],
+  "type": "object"
+}

Addedv2.1.1Oct 15, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the annotations it discloses real behavioral traits: an older ShadowGit accepts plain text only, text over the limit is silently cut, unknown ids are silently dropped, and a step's entry replaces everything previously written for that step. Those overwrite-and-drop semantics substantiate the destructiveHint and idempotentHint annotations rather than merely restating them.

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 verb and resource are front-loaded, but the body is a chain of run-on clauses with compressed phrasing ('the answer's next names them, the session's last step') that takes rereading. Nearly every clause carries information, yet the packaging obscures it.

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?

With an output schema covering returns and annotations covering safety, the description fills the important gaps: version fallback, truncation, dropped ids, replacement semantics, and the docs follow-up. The remaining gap is that the size limits are asserted but never quantified, leaving the agent to guess.

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 coverage is 100% and the schema already documents every parameter in depth (why-quote rules, excerpt constraints, body-with-card linking), so the schema does the heavy lifting. The description adds only the provenance point that ids must come from get_lens, and leaves flows and layers entirely unmentioned.

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 first clause names a specific verb and resource—writes the Lens words for a range that get_lens read—and enumerates exactly what gets written (summary, step titles and bodies, why and excerpt, card roles). It is also distinguishable from get_lens (which supplies the ids) and from write_docs (named as a later step).

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 makes the dependency explicit: ids come from get_lens, so get_lens must be called first, and it states a follow-on path (get_docs, then write_docs) when changed areas need docs words. It gives clear sequencing context but never states when not to use this tool or what happens if get_lens was skipped.

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

Deploy Server