Skip to main content
Glama

devops-linux

gitlab_ci_audit

Parse .gitlab-ci.yml stages, job dependencies (needs), cache/artifact usage, and deprecated only/except directives into a pipeline summary.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It conveys that this is a parse-and-summarize operation and lists the constructs inspected, but says nothing about how malformed or partial YAML is handled, whether it is purely local static analysis, or whether deprecation findings are advisory only.

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?

A single front-loaded sentence with no filler; every enumerated item adds discriminating detail. The dense comma list is slightly hard to scan but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations, so the description must cover both input selection and output shape. It names "a pipeline summary" without any hint of structure, and leaves the text-versus-filePath choice entirely unresolved, which is the main thing an agent needs before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters (text, filePath), and the description never mentions either. It gives no guidance on which input to supply, whether one takes precedence, or that both are optional — a real ambiguity for an agent choosing how to invoke it.

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?

Names a specific verb ("Parse") and resource (.gitlab-ci.yml), plus enumerates exactly what it extracts: stages, needs, cache/artifact usage, deprecated only/except. The GitLab-specific resource name distinguishes it from siblings like github_actions_audit, though no sibling is explicitly referenced.

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 can infer it applies when inspecting GitLab CI config. There is no when-to-use framing, no statement of what it does not cover (e.g., it summarizes rather than remediates), and no routing to alternatives for other CI systems.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources