Skip to main content
Glama

Get Mr Pipelines Tool

get_mr_pipelines_tool
Read-only

List pipelines for a merge request newest first and inspect each run’s SHA and status to confirm the MR head passed CI before merging.

Instructions

List the pipelines of a merge request, newest first.

Each pipeline carries the sha it ran on and its status (success, failed, running, ...), so you can confirm the MR head passed CI before merging.

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": {
      "project_id": "<project_id>",
      "merge_request_iid": "<merge_request_iid>"
    },
    "name": "get_mr_pipelines_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
per_pageNoResults per page (default: 20, max: 100)
project_idYesProject ID or path
merge_request_iidYesMerge request internal ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuine behavioral context beyond that: result ordering (newest first) and what each item carries (sha and status with example values), which helps the agent interpret results rather than just call the tool.

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?

Two sentences, front-loaded with the operation and ordering, followed by the practical reason to call it. Every clause earns its place and nothing is padded.

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?

A simple read-only list tool with full schema coverage, an output schema, and readOnlyHint annotations — the description supplies purpose, ordering, and result interpretation. Only a note on pagination expectations or how far back results go is missing, which is minor here.

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 description coverage is 100%, so project_id, merge_request_iid, page and per_page are already documented. The description adds only indirect meaning by tying the two required parameters to the MR-scoping concept; it says nothing extra about pagination behavior beyond the schema defaults.

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?

States a specific verb and resource with scope: 'List the pipelines of a merge request, newest first.' The MR scoping distinguishes it implicitly from the broader list_pipelines_tool, but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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?

Provides a clear intended use case — 'confirm the MR head passed CI before merging' — which tells the agent when this tool is the right choice. It stops short of naming alternatives (e.g. get_pipeline_tool for a single pipeline) or stating exclusion conditions.

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