Skip to main content
Glama
aflsolutions

ShadowGit MCP Server

by aflsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

End a ShadowGit session

end_session
Idempotent

Resume automatic snapshots for a project by ending its active ShadowGit session. Without session_id it ends whatever session is active on the project, and succeeds with nothing to do if there is none.

Instructions

Resume automatic snapshots for a project by ending its active ShadowGit session. Without session_id it ends whatever session is active on the project, and succeeds with nothing to do if there is none. Changes not saved with checkpoint are picked up by the next automatic snapshot.

Input Schema

NameRequiredDescriptionDefault
repoNoProject name or absolute path. Defaults to the current project.
session_idNoDefaults to the active session of the project

Output Schema

NameRequiredDescriptionDefault
nextNoThe step that follows a session
repoYes
endedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • addedOutput schema / properties / next
      Added value: +{
+  "description": "The step that follows a session",
+  "type": "string"
+}
  2. Changed7 schema fields changedv2.1.1
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / commitHash
      Removed value: -{
-  "description": "Commit hash from checkpoint (optional)",
-  "type": "string"
-}
    • addedInput schema / properties / repo
      Added value: +{
+  "description": "Project name or absolute path. Defaults to the current project.",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / sessionId
      Removed value: -{
-  "description": "Session ID from start_session",
-  "type": "string"
-}
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Defaults to the active session of the project",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "sessionId"
-]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "ended": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "repo": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "ended",
+    "repo"
+  ],
+  "type": "object"
+}
  3. Addedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (idempotentHint=true, destructiveHint=false), the description discloses the fate of unsaved work — anything not captured by checkpoint is picked up by the next automatic snapshot — and confirms the no-op case, which is exactly the data-loss reassurance an agent needs before ending a session. It stops short of mentioning permissions, failure modes, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences ordered by importance: purpose first, then the optional-parameter behavior, then the consequence for unsaved changes. No filler and no restatement of the title.

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, return values need not be explained, and the description covers the default targeting, the no-op case, and the post-condition for unsaved changes. Only failure/permission behavior is absent, which is a minor gap for a two-optional-parameter tool.

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 both parameters are already documented in the schema, including session_id defaulting to the active session. The description's note that omitting session_id "ends whatever session is active on the project" restates the schema rather than adding syntax or edge-case meaning, so the baseline 3 applies.

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 pairs a specific verb with a specific resource ("ending its active ShadowGit session") and frames the outcome ("resume automatic snapshots"), which is more informative than the title alone. It implies the inverse of start_session but never names that sibling, so an agent must infer the pairing rather than read it.

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 clear operating conditions: session_id is optional, the active project session is the target by default, and the call is safe to make even when no session exists ("succeeds with nothing to do if there is none"). What's missing is an explicit statement of when not to use it or a named alternative such as checkpoint.

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