Skip to main content
Glama
Sign In
cohors

cohors

by rushirb2001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

List repositories

list_repos
Read-onlyIdempotent

Return every repository's git status—branch, ahead/behind, dirty worktree, stashes, last commit, attention, and fleet summary—in one request; use it to answer fleet-wide repo questions.

Instructions

The primary "what's going on across my repos" call: returns every repo's git status — branch, ahead/behind, dirty worktree, stashes, last commit, and an attention assessment — plus a fleet summary, in one request. Use this (or fleet_summary) whenever the user asks about their repos, projects, or fleet, or what is dirty/unpushed/behind/needs attention; do NOT enumerate repos yourself with find or per-repo git. Omit selector for the whole fleet, or narrow it (e.g. {"dirty": true}). Use fields to shrink each repo to just the keys you need.

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

Input Schema

NameRequiredDescriptionDefault
sortNoOrder of the returned repos (default dirty-first).
limitNoReturn at most this many repos (after sorting).
fieldsNoProject each repo to just these top-level keys (id and name are always kept) to keep the response small. Valid keys: branch, upstream, worktree, last_commit, activity, groups, stash_count, stash_latest, remote, remote_url, operation, default_branch, last_fetch, latest_tag, assessment, path, error. Note: ahead/behind live inside `upstream`, and staged/modified/untracked inside `worktree` — request those parent keys, not the leaf names.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered structurally. The description adds real behavior beyond that: everything arrives in a single request including a fleet summary, and fields can shrink each repo to keep the response small. It doesn't mention response size limits or how the attention assessment is computed, keeping it shy of a 5.

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?

Front-loaded with the primary use case, then the trigger list, then the exclusion, then the parameter guidance. Every clause is load-bearing — no restatement of the title or schema, and the dash-delimited payload summary is dense without being cryptic.

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?

Four optional parameters, no output schema, and nested selector — yet the description effectively describes the return shape (per-repo status fields plus fleet summary) and how to keep it small. Combined with the exhaustive schema for selector, an agent has everything needed to call this correctly on the first try.

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 the baseline is 3; the description still earns a bump by giving intent-level guidance on the two non-obvious parameters — omit selector for the whole fleet versus narrow it (with an example payload), and use fields specifically to reduce response size. Note the crucial empty-selector semantics are documented in the schema rather than the description, so the description isn't carrying that alone.

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 resource and the full return payload (branch, ahead/behind, dirty worktree, stashes, last commit, attention assessment, fleet summary) in one request. It explicitly distinguishes itself from sibling fleet_summary for the same question and from the find / per-repo git route, so an agent can pick it 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?

Gives an explicit trigger (user asks about repos, projects, fleet, or what is dirty/unpushed/behind/needs attention) and an explicit anti-pattern ('do NOT enumerate repos yourself with find or per-repo git'). It also states the default behavior (omit selector for the whole fleet) versus narrowing, which is the main branching decision for this tool.

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