Skip to main content
Glama
Sign In
cohors

cohors

by rushirb2001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Uncommitted changes

changes
Read-onlyIdempotent

Lists uncommitted work across git repos—changed files with porcelain status and optional capped diffs—so you can review or summarize work in progress without running git status or diff yourself.

Instructions

What is actually uncommitted in each selected repo: the changed-file list (each path with its git porcelain status) and, with include_patch:true, a size-capped unified diff of the working tree (diffs of sensitive files like .env or key material are withheld; the file list still names them). Use this to summarize or review uncommitted work — e.g. "what's the work sitting in payments?" — instead of cd-ing in and running git status / git diff. Clean repos are omitted. Omit the selector to cover every dirty repo, or scope it (e.g. {"name": "payments"}) to one.

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": "changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorNoPredicate that selects repos across the fleet; set fields to AND them, omit a field for no constraint (ADR-024). Scope: all (bool — the whole fleet), ids[str], name (glob, e.g. "pay*"), path_glob (* stays within one path segment, ** crosses /), root, group (a config-defined cluster name, e.g. "payments"). Local state: dirty, ahead (alias unpushed), behind, diverged, no_upstream, unpublished (a branch never pushed although the repo has a remote), stale_fetch (remote not fetched for over 14 days), has_stash, detached, conflicted, in_operation (merge/rebase/… mid-flight), error, branch (exact name), attention ("any"|"notice"|"warn"|"risk"). Remote (needs a GitHub token): ci ("passing"|"failing"|"pending"|"none"), min_prs (int). Combine: any_of[selector] (OR), not (selector). The empty selector {} matches NOTHING by design — pass {"all": true} for the whole fleet.
max_bytesNoCap each repo's patch in bytes (default 20000); the patch is flagged `truncated` when cut.
include_patchNoAlso return a unified diff of the working tree per repo (default false; can be large).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds substantial context beyond them: diffs of sensitive files (.env, key material) are withheld while their paths still appear, clean repos are omitted entirely, and patches are size-capped. Those are exactly the behaviors an agent could not predict from the annotations.

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?

The first sentence is long but front-loads the core payload (file list + optional diff), and each following sentence delivers one distinct fact: use case, sensitive-file behavior, clean-repo omission, selector scoping. No filler or restatement of the title.

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?

With no output schema, the description carries the return-value burden and does so: it describes the per-path porcelain status, the diff shape and truncation flag, and the withholding rule. For a read-only tool with three parameters this leaves nothing material an agent needs unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds practical meaning: include_patch:true is the toggle that produces the diff, max_bytes defaults to 20000 and flags `truncated` when cut, and the selector can be omitted entirely or narrowed by name. The nested selector grammar itself is left to the schema, which is the right division of labor.

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 names a specific resource and scope: the uncommitted changed-file list with git porcelain status per repo, plus an optional size-capped unified diff. It explicitly frames the tool against the CLI equivalents (git status / git diff), so an agent can tell exactly what it returns without opening the schema.

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?

It states when to use it (summarize or review uncommitted work, e.g. "what's the work sitting in payments?") and names the alternative it replaces (cd-ing in and running git status / git diff). It also gives concrete scoping guidance — omit the selector for every dirty repo, or pass {"name": "payments"} for one.

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