CERN GitLab MCP Server

get_project_info

Read-only

Retrieve detailed metadata, statistics, and description for any CERN GitLab project by providing its numeric ID or full path.

Instructions

Get detailed information about a specific CERN GitLab project (metadata, statistics, description). Accepts either a numeric project ID or a full project path (e.g. 'atlas/athena').

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')

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.0Aug 28, 2026

addedInput schema / properties / project / title
```
Added value: +"Project"
```

addedInput schema / title

Added value: +"get_project_info_fnArguments"

changedOutput schema / (root)

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

First observedv0.1.6Mar 27, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description correctly matches that by describing a read-only information retrieval operation. It adds useful context about accepted input forms and the kind of content returned, but does not disclose edge-case behavior such as project-not-found handling or required permissions.

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?

The description is two sentences long, front-loads the purpose, and includes a concrete example without any filler or redundant repetition of the tool name.

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?

This is a simple single-parameter read-only tool with a full output schema, so return values need no additional explanation. The description provides the necessary calling context and acceptable input formats, making it complete for an agent to select and invoke correctly.

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%, and the schema already documents that 'project' is either a numeric ID or URL-encoded path. The description reinforces this with a human-friendly example ('atlas/athena') but adds limited new semantic meaning beyond what the input schema provides.

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 uses a specific verb ('Get') and resource ('detailed information about a specific CERN GitLab project'), with concrete output categories listed. It is clearly about a single project rather than searching or listing, though it does not explicitly differentiate itself from the similarly scoped sibling 'inspect_project'.

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?

The description establishes the context: use this when you have a specific project identifier and want metadata/statistics/description. It does not explicitly call out alternatives like 'search_projects' or 'inspect_project', but the usage context is clear and not misleading.

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

Deploy Server