Skip to main content
Glama
Sign In
dev.mcp

dev.mcp

by iwilldotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gitlab_search

Search GitLab projects or globally across issues, merge requests, commits, users, and more. Specify a scope and query to locate relevant items within a project or across the instance.

Instructions

Search in the project (GET /projects/:id/search) or globally (GET /search).

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

Input Schema

NameRequiredDescriptionDefault
scopeYesprojects, issues, merge_requests, milestones, snippet_titles, wiki_blobs, commits, blobs, users, notes.
searchYes
projectIdNoNumeric ID or path with namespace, e.g. group/project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

The explicit GET endpoints communicate that this is a read-only search operation, and the project/global distinction is genuinely behavioral. But with no annotations provided, the description carries the full burden and does not mention result shape, pagination, rate limits, or authentication requirements.

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?

The entire description is one compact sentence with the key verb front-loaded and the API detail neatly parenthesized. Every word adds useful context and there is no repetition of schema information.

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?

For a search tool with no annotations and no output schema, the description and schema together are minimally sufficient: an agent knows the required parameters, the allowed scopes, and the two invocation modes. However, it lacks return-value expectations, pagination behavior, and permission caveats, so it is not fully complete for autonomous use.

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?

The schema already describes scope and projectId, leaving only the search parameter undocumented at 67% coverage. The description adds route-level meaning by implying that projectId selects the project-scoped endpoint, which helps, but it does not describe the search term or query syntax, so it only partially compensates for the gap.

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 clearly identifies the action as 'Search' and pinpoints the resource: a specific GitLab project or GitLab globally, reinforced by the concrete API routes. It does not explicitly differentiate itself from sibling tools like gitlab_search_labels, so it stops short of a 5.

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 description gives useful context by distinguishing project-scoped search from global search, which helps an agent decide between passing projectId or omitting it. However, it offers no guidance about when to prefer this tool over alternative search tools like gitlab_search_labels, and it names no exclusions.

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