ci-watch-mcp

Overview Schema Source Related Servers Discussions Admin

Дочекатись завершення GitHub Actions CI

watch_ci

Monitor GitHub Actions CI for a commit, polling until completion, then return the final status or show failed step logs.

Instructions

Чекає, поки GitHub Actions CI завершиться для поточного (або заданого) коміту в локальному git-репозиторії, і повертає підсумок ОДНИМ викликом: ok/conclusion/url, а за провалу - одразу хвіст логу невдалих кроків (--log-failed), без окремого запиту. Заміняє ручний цикл "push -> sleep -> gh run list -> (якщо впало) gh run view --log-failed".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cwd": "<cwd>"
    },
    "name": "watch_ci"
  }
}

Input Schema

Name	Required	Description
`cwd`	Yes	Абсолютний шлях до локального клону репозиторію (з origin на GitHub)
`ref`	No	SHA коміту для перевірки; за замовчуванням поточний HEAD у cwd
`workflow`	No	Назва workflow для фільтрації (напр. "CI"), якщо в репо їх декілька
`timeout_ms`	No	Максимальний час очікування в мс, типово 300000 (5 хв), стеля 1200000 (20 хв)
`poll_interval_ms`	No	Інтервал опитування в мс, типово 5000

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the burden. It discloses key behaviors: single-call summary return, and immediate failed-step log tail on failure. It does not mention timeout behavior or authentication requirements, but the essential behavioral traits are covered well beyond what the input schema conveys.

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 description is three sentences, efficient and front-loaded. The first sentence states the core function, the second details the return behavior, and the third shows the manual cycle it replaces. No filler or redundancy.

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?

While there is no output schema and no annotations, the description provides a strong overview of inputs, behavior, and outputs, including failure handling. It does not specify timeout outcomes, but the timeout_ms parameter in the schema partially addresses that. Overall, it gives an agent sufficient context to select and invoke the tool correctly.

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 100% of parameters with detailed descriptions, so baseline is 3. The description adds minimal extra parameter context (e.g., 'current or given commit' aligns with ref, 'local git repository' aligns with cwd), but it does not meaningfully enhance the schema's already-complete parameter documentation.

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 the tool waits for GitHub Actions CI completion and returns a summary (ok/conclusion/url), with failed-step logs on failure. It uses a specific verb ('Чекає' – waits) and identifies the resource and scope (current/given commit in local git repo), making the purpose unambiguous even without sibling tools.

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?

The description explicitly frames the tool as a replacement for the manual 'push -> sleep -> gh run list -> gh run view --log-failed' cycle, clearly indicating when to use it. It provides a concrete alternative scenario and positions this tool as the streamlined single-call solution.

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

watch_ciA