Skip to main content
Glama
Sign In
patchwork-os

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

gitStash

Destructive

Temporarily stash modified and untracked files to get a clean working directory, allowing branch switches without losing progress.

Instructions

Stash current changes to get a clean working tree. Required before switching branches with uncommitted changes. Use gitStashPop to restore. Pass includeUntracked: true to also stash new files.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitStash"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNoOptional description for the stash entry
includeUntrackedNoAlso stash untracked (new) files. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations indicate destructiveHint: true, and description mentions 'get a clean working tree' implying changes are stashed away. Does not contradict annotations. Could elaborate on the destructive nature, but mentions restoration via pop.

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 sentences, all essential, front-loaded with purpose. No redundant information.

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

Completeness5/5

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

For a simple stash tool with no output schema, the description covers purpose, usage context, sibling differentiation, and parameter guidance. Complete and sufficient.

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?

Input schema covers both parameters with descriptions (100% coverage). Description adds minimal extra value, e.g., 'to also stash new files' for includeUntracked. Baseline 3 due to full schema coverage.

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 description clearly states 'Stash current changes to get a clean working tree', specifying the verb (stash) and resource (current changes). It distinguishes from sibling tools by mentioning gitStashPop for restoration.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'Required before switching branches with uncommitted changes.' Provides alternative: 'Use gitStashPop to restore.' Also advises on parameter usage for untracked files.

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