Skip to main content
Glama

get_current_user

Retrieve current user details from GitLab with an optional personal access token.

Instructions

Get current user information.

Args:
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool handler for 'get_current_user'. Calls GitLab API /user endpoint to get the authenticated user's info and returns name, username, email, and ID.
    @mcp.tool()
    async def get_current_user(token: str = None, ctx=None) -> str:
        """Get current user information.
        
        Args:
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        data = await make_gitlab_request("/user", ctx=ctx, token=token)
        if isinstance(data, dict) and "error" in data:
            return f"Error: {data['error']}"
        
        return f"User: {data['name']} (@{data['username']})\nEmail: {data['email']}\nID: {data['id']}"
  • Registration of 'get_current_user' as an MCP tool via the @mcp.tool() decorator. The function name is the tool name.
    @mcp.tool()
    async def get_current_user(token: str = None, ctx=None) -> str:
  • The helper function 'make_gitlab_request' used by get_current_user to make authenticated requests to the GitLab API.
    async def make_gitlab_request(endpoint: str, method: str = "GET", data: dict = None, ctx=None, token: str = None) -> dict[str, Any] | None:
        """Make a request to GitLab API with proper error handling."""
        # Priority: 1. Explicit token parameter, 2. Context headers, 3. Environment variable
        
        # If no explicit token provided, try to get from context
        if not token and ctx and hasattr(ctx, 'request_context') and ctx.request_context:
            # Try to get from request headers
            if hasattr(ctx.request_context, 'headers'):
                token = ctx.request_context.headers.get('GITLAB_TOKEN')
        
        # Fallback to environment variable
        if not token:
            token = os.getenv("GITLAB_TOKEN")
        
        if not token:
            return {"error": "GitLab token not provided. Please provide a token parameter, GITLAB_TOKEN in the request headers, or set the environment variable."}
        
        # Get GitLab URL (from context or environment)
        gitlab_url = os.getenv("GITLAB_URL", "https://gitlab.com")
        
        headers = {
            "PRIVATE-TOKEN": token,
            "Content-Type": "application/json"
        }
        
        url = f"{gitlab_url}/api/v4{endpoint}"
        
        async with httpx.AsyncClient() as client:
            try:
                if method == "GET":
                    response = await client.get(url, headers=headers, timeout=30.0)
                elif method == "POST":
                    response = await client.post(url, headers=headers, json=data, timeout=30.0)
                elif method == "PUT":
                    response = await client.put(url, headers=headers, json=data, timeout=30.0)
                elif method == "DELETE":
                    response = await client.delete(url, headers=headers, timeout=30.0)
                
                response.raise_for_status()
                return response.json() if response.content else {"success": True}
            except Exception as e:
                return {"error": str(e)}
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action without mentioning authentication needs, rate limits, or that it is a read-only operation. The minimal description does not compensate for the lack of annotations.

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 extremely concise with no redundant information. It is front-loaded and every sentence serves a purpose.

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 that an output schema exists, the description does not need to detail return values. However, the tool is a simple getter and the description is adequate but minimal. It lacks mention of any authentication state or error conditions, which could be important for agents without prior knowledge.

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 description adds meaning to the parameters by explaining 'token' as a GitLab Personal Access Token and noting that 'ctx' is automatically injected. This is helpful given the 0% schema description coverage. However, it does not elaborate on the format or constraints of the token.

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?

The description clearly states the verb 'Get' and the resource 'current user information', which is specific and matches the tool name. However, it does not distinguish this tool from sibling tools like 'get_project', which also use 'get'. The purpose is clear but lacks differentiation.

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, nor any exclusions or prerequisites. The description simply states what it does, leaving the agent to infer usage context from the name alone.

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

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/skmprb/gitlab-clone-mcp-server'

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