CERN GitLab MCP Server

get_release

Read-only

Retrieves detailed release information from a CERN GitLab repository, including release notes, assets, commit info, and download links. Requires a project identifier and the release tag name.

Instructions

Get detailed information about a specific release from a CERN GitLab repository. Returns release notes, assets, commit info, and download links. Requires the tag name of the release.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`project`	Yes	Project identifier — either a numeric ID (e.g. '12345') or a URL-encoded path (e.g. 'atlas/athena')
`tag_name`	Yes	The tag name of the release (e.g. 'v1.0.0')

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.3.0Aug 28, 2026

changedInput schema / properties / project / description

Previous value: -"Project identifier — either a numeric ID (e.g. '12345') or a path (e.g. 'atlas/athena')"New value: +"Project identifier — either a numeric ID (e.g. '12345') or a URL-encoded path (e.g. 'atlas/athena')"

addedInput schema / properties / project / title
```
Added value: +"Project"
```
addedInput schema / properties / tag_name / title
```
Added value: +"Tag Name"
```
addedInput schema / title
```
Added value: +"get_release_fnArguments"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_release_fnDictOutput",
+  "type": "object"
+}

First observedv0.1.6Mar 27, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The readOnlyHint annotation already covers safety, and the description adds useful context about what kind of data is returned. No authorization, pagination, or failure behavior is disclosed, but the annotation lowers the burden and no contradictions exist.

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 concise sentences communicate purpose, return contents, and the prerequisite. The text is front-loaded with the main intent and contains no filler.

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?

This is a simple read operation with full parameter schema coverage and an output schema. The description conveys the essential purpose and prerequisite; only minor enhancements like explicit sibling differentiation could make it more complete.

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 both 'project' and 'tag_name' are already well documented in the input schema. The description adds only that tag_name is required, which the schema already states, providing no additional semantic value beyond the 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 states a specific action ('Get detailed information about a specific release'), a clear resource, and the key output categories (release notes, assets, commit info, download links). This distinguishes it from siblings like list_releases and list_tags, which are collection-level operations.

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?

The description implies this tool is for fetching one release when the tag name is already known, and explicitly states the tag requirement. However, it does not give explicit when-to-use versus when-not-to-use guidance or mention alternative sibling tools.

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

Deploy Server