scout-mcp

gitlab_search

Search GitLab for public projects by query. Returns project name, description, star/fork counts, topics, and last activity. Helps discover open source projects and enterprise code not on GitHub.

Instructions

Search GitLab.com for public projects (the second largest code hosting platform). Returns name, description, stars, forks, topics, and activity. Covers enterprise OSS and projects not on GitHub.

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": {
      "query": "<query>"
    },
    "name": "gitlab_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query for GitLab projects
`per_page`	No	Results per page
`sort`	No	Sort order	stars

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 23, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided, so description must carry burden. Description states it returns specific fields and covers public repos, but does not disclose privacy policy, API rate limits, auth requirements, or any behaviors like rate limiting, pagination (though per_page is in schema), or whether results are filtered by user or permissions. Incomplete for a search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose and key differentiator. Could be slightly more concise without losing value, but efficient overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, description partially compensates by listing returned fields. However, lacks information about result structure, error handling, or usage limits. With constant sibling count (18 tools) and context signals indicating simple schema, description is minimally complete but has gaps.

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 coverage is 100%, so baseline is 3. Description does not add parameter-level details beyond schema, but schema itself is clear with descriptions for query, per_page (default, min, max), and sort (default, enum). Parameter semantics are adequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it searches GitLab.com for public projects, specifies it's the second largest code hosting platform, distinguishes from GitHub search. Mentions returned fields (name, description, stars, forks, topics, activity) and coverage (enterprise OSS, not on GitHub).

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?

Implied usage: use when looking for GitLab-hosted projects not on GitHub. But no explicit when-not-to-use or alternatives among siblings (e.g., github_search for GitHub). Context signals show sibling tools cover other platforms, but no direct exclusion guidance.

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