Skip to main content
Glama
ratheesh-aot

Clockify MCP Server

by ratheesh-aot

get_current_user

Retrieve current user profile details from Clockify to verify account access and personalize time tracking workflows.

Instructions

Get information about the current user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic. Fetches current user data from Clockify API /user endpoint and returns formatted text response with user details.
    private async getCurrentUser() {
      const user = await this.makeRequest("/user");
      return {
        content: [
          {
            type: "text",
            text: `Current user: ${user.name} (${user.email})\nActive Workspace: ${user.activeWorkspace}\nUser ID: ${user.id}`,
          },
        ],
        isError: false,
      };
    }
  • src/index.ts:253-260 (registration)
    Tool registration in the ListTools response, including name, description, and input schema (empty object).
    {
      name: "get_current_user",
      description: "Get information about the current user",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:722-723 (registration)
    Dispatch in the CallToolRequest handler switch statement that routes calls to the getCurrentUser method.
    case "get_current_user":
      return await this.getCurrentUser();
  • Input schema definition for the tool: an empty object (no parameters required).
    inputSchema: {
      type: "object",
      properties: {},
    },
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 this is a read operation ('Get'), implying it's non-destructive, but doesn't specify authentication requirements, rate limits, error conditions, or what 'information' includes (e.g., basic vs. detailed data). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, clear sentence with zero waste—it directly states the tool's purpose without fluff. It's front-loaded and appropriately sized for a simple tool with no parameters, making it easy to parse quickly.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It explains what the tool does but lacks details on return values, authentication, or differentiation from siblings. Without an output schema, the description should ideally hint at what 'information' includes, but it doesn't, leaving some context gaps for a complete understanding.

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?

The input schema has 0 parameters with 100% coverage, meaning no parameters need documentation. The description doesn't mention any parameters, which is appropriate and adds no unnecessary information. Since there are no parameters to explain, this meets the baseline expectation without compensation needed.

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 resource ('information about the current user'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its siblings (like get_workspace_users or get_clients), which also retrieve user-related data but with different scopes. The description is specific enough to understand what it does but lacks sibling 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?

The description provides no guidance on when to use this tool versus alternatives. Given the sibling tools include get_workspace_users (which might list multiple users) and other get_* tools for specific resources, there's no indication whether this tool is for authentication context, profile details, or a limited subset of user data. No exclusions or prerequisites are mentioned.

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/ratheesh-aot/clockify-mcp'

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