Skip to main content
Glama
ratheesh-aot

Clockify MCP Server

by ratheesh-aot

create_client

Add a new client to your Clockify workspace to organize projects and track time for specific customers or departments.

Instructions

Create a new client

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesWorkspace ID
nameYesClient name
archivedNoWhether client is archived (optional)

Implementation Reference

  • The handler method that implements the create_client tool. It extracts workspaceId and client data from arguments, makes a POST request to the Clockify API endpoint /workspaces/{workspaceId}/clients, and returns a success message with the created client's details.
    private async createClient(args: any) {
      const { workspaceId, ...clientData } = args;
    
      const client = await this.makeRequest(
        `/workspaces/${workspaceId}/clients`,
        "POST",
        clientData
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Client created successfully!\nID: ${client.id}\nName: ${client.name}\nArchived: ${client.archived}`,
          },
        ],
        isError: false,
      };
    }
  • src/index.ts:552-562 (registration)
    Registration of the create_client tool in the ListToolsRequestSchema handler, including the tool name, description, and input schema definition.
    name: "create_client",
    description: "Create a new client",
    inputSchema: {
      type: "object",
      properties: {
        workspaceId: { type: "string", description: "Workspace ID" },
        name: { type: "string", description: "Client name" },
        archived: { type: "boolean", description: "Whether client is archived (optional)" },
      },
      required: ["workspaceId", "name"],
    },
  • src/index.ts:785-787 (registration)
    Dispatch registration in the CallToolRequestSchema switch statement that routes create_client calls to the createClient handler method.
    case "create_client":
      if (!args?.workspaceId) throw new McpError(ErrorCode.InvalidParams, 'workspaceId is required');
      return await this.createClient(args as any);
  • TypeScript interface defining the structure of a Client object used in the codebase.
    interface Client {
      id?: string;
      name: string;
      workspaceId: string;
      archived?: boolean;
    }
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 'Create a new client', implying a write operation, but fails to describe any behavioral traits such as permissions needed, whether creation is idempotent, what happens on failure, or the expected response format. For a mutation tool with zero annotation coverage, this leaves critical gaps in understanding how the tool behaves.

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

Conciseness4/5

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

The description is a single, efficient sentence with no wasted words, making it appropriately concise. However, it is front-loaded only in the sense that it states the action immediately, but lacks any follow-up context that could enhance usability. While structurally sound, its brevity contributes to under-specification rather than optimal clarity.

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 the tool's complexity as a mutation operation with no annotations and no output schema, the description is incomplete. It does not explain what a 'client' is, how it fits into the system, what data is returned upon creation, or any error conditions. For a tool that creates a new entity, more context is needed to guide an agent effectively, especially without structured support from annotations or output schema.

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%, with all parameters documented in the schema (workspaceId, name, archived). The description adds no additional meaning beyond what the schema provides, such as explaining the purpose of 'archived' or constraints on 'name'. However, since the schema fully covers parameter descriptions, the baseline score of 3 is appropriate, as the description does not need to compensate for gaps.

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 'Create a new client' is a tautology that merely restates the tool name. It specifies the verb ('create') and resource ('client') but lacks any distinguishing details from sibling tools like 'create_project' or 'create_tag', which follow the same pattern. This minimal statement fails to clarify what a 'client' represents in this context or how it differs from other creatable entities.

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

Usage Guidelines1/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. It does not mention prerequisites (e.g., requiring a workspaceId), exclusions, or comparisons to sibling tools like 'update_client' or 'get_clients'. Without any context, an agent must infer usage solely from the name and schema, which is insufficient for effective tool selection.

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