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

mcp-gitlab-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Users Tool

list_users_tool
Read-only

Retrieve and filter GitLab users by active status, username, or search term, with pagination controls to find accounts across a GitLab instance.

Instructions

List GitLab users.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
activeNoOnly return active users (default: true)
searchNoSearch for users by name or email
per_pageNoResults per page, max 100 (default: 20)
usernameNoFilter by exact username

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.3/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds no behavioral context beyond that annotation, such as pagination defaults, filtering behavior, or what the listing returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no wasted words, but it is under-specified rather than appropriately concise for a tool with five optional filters. It is front-loaded and easy to parse, but too minimal to add value.

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?

The tool has five parameters, a rich schema, an output schema, and many siblings, yet the description provides no scope or usage distinctions. Structured fields cover parameter and return details, but the description leaves the agent unable to confidently choose this tool over get_user_tool or search_global_tool.

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 all five parameters (page, active, search, per_page, username) are already documented in the input schema. The description adds no parameter meaning beyond the schema, but baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List GitLab users' simply restates the tool name and title with the product name added; it does not distinguish this tool from siblings like get_user_tool or get_current_user_tool. The verb and resource are clear, but the purpose statement is essentially tautological rather than informative.

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 guidance on when to use this tool versus get_user_tool, get_current_user_tool, or search_global_tool. The agent must infer from the name alone that this is for enumerating users rather than fetching a specific known user.

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