Skip to main content
Glama

get_release

Read-onlyIdempotent

Retrieve detailed release information from a CERN GitLab repository by tag name, including release notes, assets, commit info, and download links.

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.

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": "<project>",
      "tag_name": "<tag_name>"
    },
    "name": "get_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject identifier — either a numeric ID (e.g. '12345') or a namespace/project path (e.g. 'atlas/athena')
tag_nameYesThe tag name of the release (e.g. 'v1.0.0')

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / project / description
      Previous value: -"Project identifier — either a numeric ID (e.g. '12345') or a URL-encoded path (e.g. 'atlas/athena')"New value: +"Project identifier — either a numeric ID (e.g. '12345') or a namespace/project path (e.g. 'atlas/athena')"
  2. Changed5 schema fields changedv0.3.0
    • 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"
      +}
  3. First observedv0.1.6

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description adds the shape of the payload (release notes, assets, commit info, download links), which is useful context, but says nothing about error behavior for missing tags or permission scope.

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?

Three short sentences, front-loaded with the action and resource, followed by return content and the required input. No filler, though the final sentence largely duplicates the schema's required field list.

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 an output schema, rich annotations, and full schema parameter documentation, the description only needs to frame the fetch and its purpose, which it does. The minor gap is the lack of routing guidance relative to list_releases and list_tags in a 15-tool sibling set.

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%, including examples for both the project identifier and the tag name, so the schema carries the parameter burden. The description only restates that a tag name is required and says nothing about the project parameter or accepted tag formats beyond what is already documented.

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?

The description gives a specific verb and resource — 'Get detailed information about a specific release from a CERN GitLab repository' — and the word 'specific' implicitly contrasts with the sibling list_releases. It never names the sibling or states that list_releases should be used to discover tags first, so differentiation is implied rather than explicit.

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: the agent can infer this is for fetching one release once a tag is known. There is no explicit when-to-use vs list_releases/list_tags guidance and no stated prerequisites such as resolving a tag name before calling.

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