Skip to main content
Glama

gitlab_pipeline_health

Read-onlyIdempotent

Assess pipeline stability by aggregating success rate over 7 and 30 days with a trend indicator for any branch or source, suitable for stand-ups and on-call hand-offs.

Instructions

Aggregate success rate over 7 and 30 days with a trend indicator.

Great for stand-ups and on-call hand-offs. Returns success rate %, totals, last-10 statuses and a trend (up/down/flat).

Emits progress via the MCP Context (info log + report_progress) — useful in IDEs that show per-tool progress bars.

Examples: - "How stable is master" → default (ref='master', source='schedule') - "Push-driven pipeline health" → source='push' - Don't use for a single pipeline — use gitlab_get_pipeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoBranch to analyse.master
sourceNoPipeline source to include (typically 'schedule' or 'push').schedule
project_pathNoGitLab project path (e.g. 'my-org/my-repo'). When omitted, the default from GITLAB_PROJECT_PATH env var is used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYes
refYes
sourceYes
rate_7dYes
rate_30dYes
trendYes
total_7dYes
success_7dYes
failed_7dYes
total_30dYes
success_30dYes
failed_30dYes
last_10_statusesYes
generated_atYes
Behavior4/5

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

Discloses progress emission via MCP Context (info log + report_progress) beyond the readOnly/idempotent annotations. Does not mention data freshness or rate limits, but the behavioral context is strong.

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?

Well-structured with bullet points and examples; concise but includes essential details. Minor wordiness (e.g., 'Great for stand-ups') but overall efficient.

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?

Explains what the tool returns (success rate %, totals, last-10 statuses, trend indicator) despite having an output schema. Covers use cases and parameter behavior completely for a health-report tool.

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?

All three parameters have schema descriptions (100% coverage). The description adds semantic examples (e.g., ref='master', source='schedule') and clarifies the project_path default from env var, enhancing meaning beyond schema.

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 it aggregates success rate over 7 and 30 days with a trend indicator, explicitly differentiating from single-pipeline tools like gitlab_get_pipeline.

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?

Provides explicit when-to-use (stand-ups, on-call hand-offs) and when-not ('Don't use for a single pipeline — use gitlab_get_pipeline'), with concrete examples for parameter values.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mshegolev/gitlab-ci-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server