Skip to main content
Glama

gitlab_get_user

Retrieve detailed information about a specific user from a GitLab account by providing the user ID, facilitating user management and access control.

Instructions

Get details of a specific user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesThe ID of the user

Implementation Reference

  • The main handler function for the 'gitlab_get_user' tool, which retrieves user details by ID using the usersGroupsManager.
    export const getUser: ToolHandler = async (params, context) => {
      const { user_id } = params.arguments || {};
      if (!user_id) {
        throw new McpError(ErrorCode.InvalidParams, 'user_id is required');
      }
      
      const data = await context.usersGroupsManager.getUser(user_id as number);
      return formatResponse(data);
    };
  • The input schema definition for the 'gitlab_get_user' tool, specifying the required 'user_id' parameter.
      name: 'gitlab_get_user',
      description: 'Get details of a specific user',
      inputSchema: {
        type: 'object',
        properties: {
          user_id: {
            type: 'number',
            description: 'The ID of the user'
          }
        },
        required: ['user_id']
      }
    },
  • Registration of the 'gitlab_get_user' tool mapping to the getUser handler function from usersGroupsHandlers.
    gitlab_get_user: usersGroupsHandlers.getUser,
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get details' which implies a read-only operation, but doesn't specify if it requires authentication, rate limits, error handling, or what the return format looks like (e.g., JSON structure). This leaves significant gaps for a tool with no annotation coverage.

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, efficient sentence that is front-loaded and wastes no words. It directly conveys the core purpose without unnecessary elaboration, making it appropriately sized for a simple tool.

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?

Given no annotations and no output schema, the description is incomplete for a tool that retrieves user details. It doesn't explain what details are returned, potential errors, or usage context. For a read operation with no structured output information, more guidance is needed to be fully helpful to an agent.

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 input schema has 100% description coverage, with 'user_id' clearly documented as 'The ID of the user' of type number. The description adds no additional meaning beyond this, such as format examples or constraints. With high schema coverage, the baseline is 3, as the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Get details of a specific user' clearly states the verb ('Get') and resource ('user'), but it's vague about what 'details' entails and doesn't distinguish this tool from sibling tools like 'gitlab_get_group' or 'gitlab_get_project', which follow a similar pattern. It avoids tautology by not merely restating the name, but lacks specificity.

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 guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify if this is for retrieving a single user by ID while 'gitlab_list_users' is for listing all users, or mention any prerequisites like authentication. The description implies usage but offers no explicit context or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rifqi96/mcp-gitlab'

If you have feedback or need assistance with the MCP directory API, please join our Discord server