Skip to main content
Glama
zereight

gitlab mcp

by zereight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discover_tools

Read-only

Discover and activate additional GitLab tool categories for the current session. List available categories or specify one to enable its tools, returning an active-tool summary.

Instructions

Discover and activate additional tool categories for this session. Available categories: merge_requests, issues, repositories, branches, projects, labels, ci, groups, pipelines, milestones, wiki, releases, tags, users, workitems, webhooks, search, variables, dependency_proxy, vulnerabilities, orbit. Already-active categories are listed in the response. Use this when a needed opt-in category is not currently exposed; omit category to inspect available categories, then call it with a category to activate that group for the current session. It changes only the session's tool registry, returns the active-tool summary, and does not change GitLab data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoToolset category to activate (e.g. 'pipelines', 'wiki'). Omit to list available categories.
jmespathNoOptional JMESPath expression filtering the JSON result before return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.66
    • addedInput schema / properties / jmespath
      Added value: +{
+  "description": "Optional JMESPath expression filtering the JSON result before return.",
+  "type": "string"
+}
  2. Addedv2.1.45
  3. Removedv2.1.43
  4. Addedv2.1.18
  5. Removedv2.1.14
  6. Addedv2.1.11
  7. Removedv2.1.10
  8. Addedv2.1.9

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already provide readOnlyHint and openWorldHint, but the description adds critical context: it only changes the session's tool registry, returns an active-tool summary, and does not modify GitLab data. This goes beyond the annotations and fully discloses side effects, so the agent can safely invoke it without concern for persistence.

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?

The description is front-loaded with the core purpose and includes a necessary list of categories. While the category list is long, it is directly relevant for the agent to know valid values. The phrasing is efficient, with no fluff, though it could be slightly tightened by moving the category list to the end.

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

Completeness5/5

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

For a meta-tool with no output schema, the description explains the return (active-tool summary), the session-scoped mutation, and the two-phase usage pattern. All information needed to decide and call the tool correctly is present, including the exact categories and the no-data-change guarantee.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are well-documented. The description adds value by enumerating all valid category names and explaining the omission behavior for `category`, which is not in the schema. It also clarifies the optional JMESPath filtering role implicitly by context, though the schema already covers it.

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?

The description clearly states the tool discovers and activates tool categories, lists the exact available categories, and explains its meta-purpose of managing the session's tool registry. It distinguishes itself from sibling tools by being the only one that modifies the available toolset, not operating on GitLab data.

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

Usage Guidelines5/5

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

Explicitly states when to use: when a needed opt-in category is not exposed, and gives a two-step workflow: omit `category` to inspect, then call with a category to activate. It also clarifies session-scoped behavior and that it does not alter GitLab data, leaving no ambiguity about alternatives.

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