Skip to main content
Glama
Sign In
mcp-gitlab-crunchtools

mcp-gitlab-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search Project Tool

search_project_tool
Read-only

Search a specific GitLab project for matching issues, merge requests, commits, wiki pages, notes, or code, with scope selection and pagination.

Instructions

Search within a specific GitLab project.

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": {
      "project_id": "<project_id>",
      "search": "<search>"
    },
    "name": "search_project_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
scopeNoSearch scope (issues, merge_requests, milestones, wiki_blobs, commits, blobs, notes)blobs
searchYesSearch query string
per_pageNoResults per page, max 100 (default: 20)
project_idYesProject ID or path

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.9/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, so the behavioral bar is lower, but the description adds nothing: it omits that the default scope is 'blobs' (i.e., searches file contents, not issues or commits), that results are paginated, and what a result contains despite an output schema existing.

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?

A single tight sentence with no wasted words and the scoping constraint front-loaded. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

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

Completeness2/5

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

With five parameters, a non-obvious default scope ('blobs') that materially changes what gets searched, and a sibling global-search tool, the description should say more. It does not mention the scope default, pagination, or when to prefer search_global_tool, leaving key decisions to the schema.

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 parameter documentation is fully handled by the schema and a baseline 3 applies. The description contributes no additional meaning about project_id vs. path, scope values, or pagination limits.

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') and scope ('within a specific GitLab project'), which is enough to tell it apart from search_global_tool in principle. However it never names the sibling that performs the unscoped version, so differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of search_global_tool as the alternative for cross-project searches. An agent must infer from the tool name alone whether to scope the search or search globally.

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

Deploy Server

Other Tools