Skip to main content
Glama

search_lhcb_stack

Read-onlyIdempotent

Search code snippets across an LHCb software stack and automatically resolve the correct Git references for its projects.

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.

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": {
      "search_term": "<search_term>",
      "stack": "<stack>"
    },
    "name": "search_lhcb_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoOptional: Override the Git branch or tag to search within. If omitted, uses the branch matching the stack.
pageNoPage number to retrieve
scopeNo'blobs' searches file content (default), 'filenames' searches only file namesblobs
stackYesName of the software stack (e.g. 'sim11')
projectNoOptional: limit search to a specific project (ID or path). If omitted, searches across all public projects using default refs.
per_pageNoNumber of results to return
search_termYesThe code or text to search for

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changedv0.3.0
    • 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"
      +}
  2. First observedv0.1.6

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that Git refs are resolved automatically per stack — but says nothing about pagination behavior, result ordering, or how a bad stack name is handled.

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 short sentences, zero filler, with the scoping constraint front-loaded before the resolution behavior. The stack example duplicates the schema's example but at negligible cost.

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?

An output schema exists and annotations are rich, so the description needn't explain return values or safety. For a seven-parameter search tool it is nearly complete, though it omits the default scope (content vs filenames) and default result count that shape what the agent gets back.

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 every one of the seven parameters is already documented in the schema, including the ref/stack override relationship and the scope enum. The description's remark about automatic Git ref resolution restates what the 'ref' property already says, so it adds no meaning beyond structured data.

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+resource pair ('Search for code snippets') and constrains it to a scoped target ('within a specific LHCb software stack (e.g., 'sim11')'). That scope implicitly distinguishes it from the general search_code sibling, but no sibling is named, so an agent must infer the distinction.

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 it should reach for this tool when the work is tied to a named stack. There is no explicit when-not guidance, no mention of search_code or search_projects as alternatives, and no stated prerequisites for a valid stack name.

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