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

gitlab-mcp-server

by kopiloto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_groups

Retrieve GitLab groups accessible to your account. Optionally filter by groups you own and set the number of results.

Instructions

List GitLab groups accessible to the authenticated user.

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": "list_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownedNoOnly list groups owned by the authenticated user
per_pageNoNumber of groups to return (max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description partially carries the burden of behavioral disclosure. It indicates that the tool is a read operation by implying listing, but it does not disclose pagination behavior, rate limits, or any side effects. The mention of 'accessible to the authenticated user' adds minimal transparency.

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 description is a single sentence with no redundant words. It conveys the essential purpose efficiently without any waste.

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 the tool's simplicity (0 required params, no output schema), the description is barely adequate. It omits details about return format, pagination limits, or common use cases. However, the schema covers parameters, and the purpose is clear, so it achieves a minimal completeness.

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 explains both parameters adequately. The description adds no additional context or constraints beyond what the schema provides, thus meeting the baseline of 3.

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 verb 'List' and the resource 'GitLab groups' with a specific scope 'accessible to the authenticated user'. This distinguishes it from sibling tools that list different entities, such as list_projects or list_merge_requests.

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?

The description provides no guidance on when to use this tool versus alternatives, such as list_group_projects. It does not mention prerequisites, constraints, or exclusions. For a list operation, it lacks explicit context for selection.

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