Skip to main content
Glama
Sign In
cohors

cohors

by rushirb2001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Launchpad

launchpad
Read-onlyIdempotent

Find what to work on across repos: view waiting tasks, available run/test flows, and which repositories are not set up yet.

Instructions

What each repo OFFERS and what work is WAITING in it: its committed .cohors/ contribution (summary, group, declared flows, repo-shipped agents, tasks) plus flows auto-detected from npm/cargo/uv/Makefile/gradle manifests. Use for "what should I work on", "what's on my plate across repos", "how do I run/test X", or to see which repos are not set up yet (configured: false). Omit selector for the whole fleet. Open tasks come back most-urgent first.

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

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.
include_doneNoAlso return finished tasks (default false).
only_configuredNoSkip repos without a .cohors/ contribution (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real context beyond them: the returned payload contents, the configured:false signal, and the ordering guarantee that open tasks come back most-urgent first. It does not disclose cost, token requirements for the remote predicates, or failure behavior, which would be needed for 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.

Conciseness4/5

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

The payload contents are front-loaded, followed by the use-case triggers and the scoping default; the quoted query examples earn their place as routing cues. It is a single dense paragraph with little waste, though the parenthetical field list is slightly listy.

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?

For a read-only three-parameter tool with a deeply nested selector schema and no output schema, the description supplies the essentials: what is returned, how results are ordered, and the empty-vs-omitted selector distinction. Gaps remain around token-gated remote predicates and result volume, but nothing critical to invoking it correctly is missing.

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 the selector property is exhaustively documented, so the schema already carries the parameter burden and baseline 3 applies. The description does add one genuinely useful nuance not obvious from the schema alone — omitting the selector means the whole fleet — which prevents an agent from passing {} and getting nothing, but include_done and only_configured get no treatment in the description.

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 states a specific resource and scope: each repo's committed .cohors/ contribution (summary, group, flows, agents, tasks) plus flows auto-detected from npm/cargo/uv/Makefile/gradle manifests. That is concrete enough for an agent to know exactly what comes back. It does not explicitly differentiate itself from siblings like fleet_summary, overview, or get_repo, which keeps it from a 5.

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 four concrete trigger queries ("what should I work on", "what's on my plate across repos", "how do I run/test X", unconfigured repos) and states the default scoping rule (omit selector for the whole fleet). There is no explicit when-not guidance or named alternative for overlapping tools such as fleet_summary or overview, so it stops short of a 5.

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