Skip to main content
Glama

search_projects

Read-onlyIdempotent

Search public CERN GitLab projects by keywords, topics, or programming language to discover High Energy Physics code, analysis frameworks, and physics tools.

Instructions

Search for public CERN GitLab projects (which contain repositories, issues, wikis, etc.) by keywords, topics, or programming language. Useful for discovering HEP code, analysis frameworks, and physics tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNoSort orderdesc
queryNoSearch query string (matches project name, description, etc.)
topicNoFilter by project topic/tag (e.g. 'physics', 'root', 'atlas')
sort_byNoSort results by this fieldlast_activity_at
languageNoFilter by primary programming language (e.g. 'python', 'c++', 'java')
per_pageNoNumber of results to return

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changedv0.3.0
    • addedInput schema / properties / language / default
      Added value: +""
    • addedInput schema / properties / language / title
      Added value: +"Language"
    • addedInput schema / properties / order / default
      Added value: +"desc"
    • changedInput schema / properties / order / description
      Previous value: -"Sort order (default: desc)"New value: +"Sort order"
    • addedInput schema / properties / order / title
      Added value: +"Order"
    • 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 / query / default
      Added value: +""
    • addedInput schema / properties / query / title
      Added value: +"Query"
    • addedInput schema / properties / sort_by / default
      Added value: +"last_activity_at"
    • changedInput schema / properties / sort_by / description
      Previous value: -"Sort results by this field (default: last_activity_at)"New value: +"Sort results by this field"
    • addedInput schema / properties / sort_by / title
      Added value: +"Sort By"
    • addedInput schema / properties / topic / default
      Added value: +""
    • addedInput schema / properties / topic / title
      Added value: +"Topic"
    • removedInput schema / required
      Removed value: -[]
    • addedInput schema / title
      Added value: +"search_projects_fnArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "result": {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "title": "Result",
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "title": "search_projects_fnOutput",
      +  "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 readOnly, idempotent, open-world and non-destructive behavior, so the description only needs to add context. It usefully narrows scope to public projects and explains what a project object encompasses, but says nothing about pagination, result caps, or whether archived/private projects are excluded.

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 tight sentences with the resource and scope front-loaded and the use case following. No filler or redundancy.

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 and full annotation coverage, the description carries only a light burden, and it covers what is searched and why. The remaining gap is operational detail such as pagination or result limits, which is minor for a read-only search tool.

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 the schema already documents all six parameters including enums and defaults. The description adds a loose mapping ('keywords, topics, or programming language' to query/topic/language) but says nothing about order, sort_by, or per_page beyond what the 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?

States a specific verb ('search') plus a well-scoped resource ('public CERN GitLab projects') and clarifies that projects contain repositories, issues and wikis, which separates it from search_code and search_issues by implication. It stops short of naming those siblings explicitly, so the differentiation is inferred 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence gives a use context ('discovering HEP code, analysis frameworks, and physics tools'), which implies when to reach for it. There is no explicit when-not guidance and no reference to the alternative search tools (search_code, search_issues, search_lhcb_stack) that an agent must choose between.

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