Skip to main content
Glama
DiversioTeam

ClickUp MCP Server

by DiversioTeam

get_current_user

Retrieve details of the currently authenticated ClickUp user to verify identity and access permissions for task management operations.

Instructions

Get details of the currently authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main tool handler function that fetches and formats the current user data using the ClickUpClient.
    async def get_current_user(self) -> Dict[str, Any]:
        """Get details of the currently authenticated user."""
        user = await self.client.get_current_user()
    
        return {
            "id": user.get("id"),
            "username": user.get("username"),
            "email": user.get("email"),
            "initials": user.get("initials"),
            "color": user.get("color"),
            "profilePicture": user.get("profilePicture"),
            "role": user.get("role"),
        }
  • Input schema definition for the get_current_user tool, which requires no parameters.
    Tool(
        name="get_current_user",
        description="Get details of the currently authenticated user",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
  • Registers the get_current_user method as a tool handler in the internal tools dictionary.
    "get_task_analytics": self.get_task_analytics,
    # User management
    "list_users": self.list_users,
    "get_current_user": self.get_current_user,
    "find_user_by_name": self.find_user_by_name,
  • Helper method on ClickUpClient that makes the API request to retrieve the current user data.
    async def get_current_user(self) -> Dict[str, Any]:
        """Get the current authenticated user."""
        data = await self._request("GET", "/user")
        return data.get("user", {})

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only states 'Get details' without specifying what details, side effects, or authentication requirements. Minimal disclosure.

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?

Single sentence, front-loaded, no wasted words. Perfectly concise.

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?

For a simple tool with no params or output schema, the description is adequate but vague on return values. Could mention typical fields like username, email, etc.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so schema coverage is 100%. Description adds no parameter info, but baseline for 0 params is 4.

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 'Get' and resource 'details of the currently authenticated user', distinguishing it from sibling 'get_user' which requires a user ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

No explicit guidance on when to use vs alternatives, but the purpose is clear. Lacks when-not-to-use or alternative references.

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