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

mcp-gitlab-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Groups Tool

list_groups_tool
Read-only

Lists GitLab groups available to the API token, with options to filter owned or top-level groups, search by name, and paginate results.

Instructions

List GitLab groups accessible by the API token.

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_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
sortNoSort direction (asc, desc)asc
ownedNoOnly list groups owned by the authenticated user
searchNoSearch for groups by name
order_byNoOrder by field (name, path, id)name
per_pageNoResults per page, max 100 (default: 20)
top_level_onlyNoOnly list top-level groups

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating call, so the bar is lower. The description adds the useful detail that results are limited by the token's access, but it says nothing about pagination defaults, result caps, or how nested/subgroups appear — context an agent listing groups would want.

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 front-loaded sentence with no filler. It is efficient, though arguably under-specified rather than genuinely tight — the brevity comes at the cost of useful context.

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?

An output schema exists, so return-value explanation isn't needed, and 100% schema coverage covers parameters. What's missing is any framing of this list's relationship to the group-detail and group-projects siblings, which for a 60+ tool server is the main thing a description must add.

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%, with all seven parameters (page, per_page, sort, order_by, search, owned, top_level_only) documented inline including defaults. Per the rubric this sets a baseline of 3; the description adds nothing beyond it.

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+resource ('List GitLab groups') and scopes it to what the API token can access. It does not explicitly distinguish itself from get_group_tool or list_group_projects_tool, which are the nearest siblings, so it falls 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 Guidelines2/5

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

No when-to-use guidance, no exclusions, and no mention of alternatives such as get_group_tool for a single group. The only implicit signal is 'accessible by the API token', which hints at a permission scope but gives no selection criteria.

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