CERN GitLab MCP Server

search_lhcb_stack

Read-only

Search for code snippets within a specific LHCb software stack, automatically resolving correct Git references for projects in that stack.

Instructions

Search for code snippets within a specific LHCb software stack (e.g., 'sim11'). Automatically resolves the correct Git references for projects in that stack.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ref`	No	Optional: Override the Git branch or tag to search within. If omitted, uses the branch matching the stack.
`page`	No	Page number to retrieve
`scope`	No	'blobs' searches file content (default), 'filenames' searches only file names	blobs
`stack`	Yes	Name of the software stack (e.g. 'sim11')
`project`	No	Optional: limit search to a specific project (ID or path). If omitted, searches across all public projects using default refs.
`per_page`	No	Number of results to return
`search_term`	Yes	The code or text to search for

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedv0.3.0Aug 28, 2026

addedInput schema / properties / page / default
```
Added value: +1
```

changedInput schema / properties / page / description

Previous value: -"Page number to retrieve (default: 1)"New value: +"Page number to retrieve"

addedInput schema / properties / page / title
```
Added value: +"Page"
```
addedInput schema / properties / per_page / default
```
Added value: +20
```

changedInput schema / properties / per_page / description

Previous value: -"Number of results to return (default: 20, max: 100)"New value: +"Number of results to return"

addedInput schema / properties / per_page / title
```
Added value: +"Per Page"
```
addedInput schema / properties / project / default
```
Added value: +""
```

changedInput schema / properties / project / description

Previous value: -"Optional: limit search to a specific project. Either a numeric ID or path (e.g. 'lhcb/Boole'). If omitted, searches across all public projects using default refs."New value: +"Optional: limit search to a specific project (ID or path). If omitted, searches across all public projects using default refs."

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

changedInput schema / properties / ref / description

Previous value: -"Optional: Override the Git branch or tag to search within. If omitted, automatically uses the branch matching the stack if applicable."New value: +"Optional: Override the Git branch or tag to search within. If omitted, uses the branch matching the stack."

addedInput schema / properties / ref / title
```
Added value: +"Ref"
```
addedInput schema / properties / scope / default
```
Added value: +"blobs"
```

changedInput schema / properties / scope / description

Previous value: -"Search scope: 'blobs' searches file content (default), 'filenames' searches only file names"New value: +"'blobs' searches file content (default), 'filenames' searches only file names"

addedInput schema / properties / scope / title
```
Added value: +"Scope"
```
addedInput schema / properties / search_term / title
```
Added value: +"Search Term"
```

changedInput schema / properties / stack / description

Previous value: -"Name of the software stack (e.g., 'sim11')"New value: +"Name of the software stack (e.g. 'sim11')"

addedInput schema / properties / stack / title
```
Added value: +"Stack"
```

addedInput schema / title

Added value: +"search_lhcb_stack_fnArguments"

changedOutput schema / (root)

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

First observedv0.1.6Mar 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare the operation is read-only and open-world, so safety is covered. The description adds meaningful behavioral context beyond annotations: it automatically resolves the correct Git references for stack projects, which is non-obvious and affects how callers should think about the ref parameter.

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 with no wasted words. The core purpose is front-loaded and the most significant behavioral nuance, automatic ref resolution, is included without padding.

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?

Given the rich input schema, annotations, and presence of an output schema, the description covers the essential purpose and the main non-obvious behavior. It could be slightly more complete by distinguishing itself from the sibling search_code tool, but what is needed to invoke it correctly is largely present.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying the relationship between stack and ref: the stack determines the default Git reference, and the tool resolves it automatically. This goes beyond the individual parameter descriptions.

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 clearly states the tool searches for code snippets within a specific LHCb software stack and adds the distinctive behavior of automatically resolving Git references. It effectively distinguishes itself from general code search tools like search_code, though it does not explicitly name any sibling as an alternative.

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 implies a clear use case: searching code within an LHCb stack without manually specifying Git refs. However, it does not explicitly state when not to use this tool or mention alternative tools such as search_code or search_projects, so it stops short of full routing guidance.

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

Deploy Server