ShadowGit MCP Server

Overview Schema Source Related Servers Discussions Admin

Write a range's Lens words

write_lens_words

DestructiveIdempotent

Write the words displayed in ShadowGit Lens for a get_lens range: summary, step titles/bodies, why quotes, excerpts, and card roles, using the ids get_lens provided.

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.

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	Default
`repo`	Yes
`applied`	Yes
`ignored`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.1/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real behavioral disclosure beyond them: a step entry replaces everything previously written for that step, older ShadowGit accepts plain text alone, over-limit text is silently cut, unknown ids are silently dropped, and a card's role persists into later ranges while its code is unchanged. These silent-truncation and silent-drop semantics are exactly the traits an agent must know before invoking.

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?

Front-loaded with the purpose in the first sentence, and the backward-compatibility and truncation rules are packed into a compact second sentence with no filler. The sentences are dense and slightly convoluted, which costs a point.

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 present there is no need to describe return values, and the description covers mutation semantics, id sourcing, truncation and unknown-id handling, and persistence into later ranges. What is still missing is explicit invocation prerequisites (e.g. that get_lens must be read first to obtain valid ids).

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 baseline is 3. The prose restates the payload shape (summary, steps with title/body/why/excerpt, components with roles) and adds the tie that ids come from get_lens, but contributes little syntax or constraint detail beyond what the schema already documents.

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?

States a specific verb and resource: it writes the user-facing Lens words (summary, step titles/bodies, why, excerpts, card roles) for a range that get_lens read. It is unambiguous about being the write-side counterpart of get_lens, so an agent can tell it apart from the read tool without opening a schema.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: ids must come 'by the ids get_lens gave', which establishes a get_lens-first workflow. There is no explicit when-to-use/when-not-to-use statement, no prerequisite spelled out, and no comparison against other siblings such as checkpoint or end_session.

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

Deploy Server