Skip to main content
Glama

search_issues

Read-onlyIdempotent

Search CERN GitLab issue discussions to understand library usage, resolve common errors, and verify feature support across projects or within a specific project.

Instructions

Search for issues and discussions in CERN GitLab projects. Useful for understanding how a library is used, finding solution to common errors, or checking if a feature is supported.

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>"
    },
    "name": "search_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoFilter by issue stateall
projectNoOptional: limit search to a specific project. If omitted, searches across all projects you have access to.
per_pageNoNumber of results to return
search_termYesKeywords to search for in issue titles and descriptions

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.3.0
    • addedInput schema / properties / per_page / default
      Added value: +10
    • changedInput schema / properties / per_page / description
      Previous value: -"Number of results to return (default: 10, max: 100)"New value: +"Number of results to return"
    • addedInput schema / properties / per_page / maximum
      Added value: +100
    • addedInput schema / properties / per_page / minimum
      Added value: +1
    • addedInput schema / properties / per_page / title
      Added value: +"Per Page"
    • addedInput schema / properties / project / default
      Added value: +""
    • addedInput schema / properties / project / title
      Added value: +"Project"
    • addedInput schema / properties / search_term / title
      Added value: +"Search Term"
    • addedInput schema / properties / state / default
      Added value: +"all"
    • changedInput schema / properties / state / description
      Previous value: -"Filter by issue state (default: all)"New value: +"Filter by issue state"
    • addedInput schema / properties / state / title
      Added value: +"State"
    • addedInput schema / title
      Added value: +"search_issues_fnArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "search_issues_fnDictOutput",
      +  "type": "object"
      +}
  2. First observedv0.1.6

TDQS

A3.8/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, so the safety profile is fully covered by structured data. The only behavioral detail the description adds is that discussions are included alongside issues, which the schema's issue-oriented state filter does not hint at. Pagination limits and result ordering behavior are left unstated.

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, no redundancy, with the core action stated first and the motivating use cases second. Every clause contributes either scope or selection guidance.

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?

For a simple read-only search tool with full schema coverage and an output schema, the description supplies everything needed to decide to call it. The minor gap is that "discussions" are promised in the description but no parameter or schema field addresses them, leaving an agent unsure how discussion results are filtered or returned.

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%: state enum, project scoping, per_page bounds, and the search_term semantics are all documented in the schema itself. The description adds no syntax, format, or scoping detail beyond that, so the baseline of 3 applies.

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 pairs a specific verb ("Search") with a specific resource ("issues and discussions in CERN GitLab projects"), which is distinct from siblings like search_code, search_projects, and search_lhcb_stack by resource type. It does not name those alternatives explicitly, so differentiation is inferred from the resource noun rather than stated.

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?

Three concrete use cases are given (understanding library usage, resolving common errors, checking feature support), which tells an agent when this tool is the right choice. It stops short of exclusions such as "use search_code when you need implementation details instead of reported problems."

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