Skip to main content
Glama

CI status

ci_status
Read-onlyIdempotent

Retrieve GitHub Actions status for a repository: recent default-branch workflow runs and checks for the current open pull request, naming failing jobs.

Instructions

GitHub Actions for a repository: the newest run of each workflow on its default branch, and the checks of the newest session's open pull request, with the failing jobs named. Needs GitHub connected in Caprock's Settings; read through Caprock, which already holds that connection.

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

Input Schema

NameRequiredDescriptionDefault
repoNoA directory inside the repository; defaults to the directory this server was started in (normally the project the agent is working in).

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 declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: the authentication prerequisite, the fact that reads are proxied through Caprock's stored connection, and the exact scope of data surfaced (default branch only, newest session's open PR only). It stops short of noting behavior when no workflows or no open PR exist.

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?

Two sentences, front-loaded with the payload description before the prerequisite. The clause 'read through Caprock, which already holds that connection' is slightly redundant with the preceding sentence but does clarify the auth model, so it largely earns its place.

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?

With no output schema, the description carries the burden of conveying return shape, and it does so concretely: per-workflow newest runs, PR checks, and named failing jobs. The auth prerequisite is included. Only edge cases (no workflows, no open PR, non-default-branch questions) are unaddressed.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already explains that 'repo' is a directory inside the repository and defaults to the server's start directory. The description adds nothing about the parameter, which is acceptable at full coverage but is the baseline rather than added value.

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 the resource (GitHub Actions for a repository) and specifies exactly what is returned: the newest run of each workflow on the default branch, the checks of the newest session's open pull request, and the names of failing jobs. That level of specificity makes it unmistakable against the sibling memory/session tools.

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

Usage Guidelines3/5

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

Usage is only implied — an agent infers it is for checking CI health, and the prerequisite 'Needs GitHub connected in Caprock's Settings' is stated. There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named, though the sibling set is unrelated enough that ambiguity is low.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.