Skip to main content
Glama
Sign In
@lewinnovation/clockify-mcp-server

@lewinnovation/clockify-mcp-server

by lewinnovation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_time_entry

Log a new time entry in a Clockify workspace with start and end times, plus optional project, task, tags, billable status, and description.

Instructions

Creates a time entry in a workspace (POST /v1/workspaces/{workspaceId}/time-entries).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>",
      "entry": "<entry>"
    },
    "name": "create_time_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryYesFields for the new time entry.
workspace_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but only implies a write via 'Creates'. It says nothing about required permissions, whether the entry becomes a running timer, duplicate/overlap handling, or what happens on validation failure for the 8 sub-fields.

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

Conciseness3/5

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

A single sentence with no padding and the endpoint front-loaded is efficient, but it is under-specified rather than genuinely concise, and the URL adds little an agent can act on.

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?

For a mutation tool with no annotations, no output schema, and a nested object parameter set, the definition is far too thin: auth requirements, success response shape, and validation rules for the nested fields are all absent.

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

Parameters2/5

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

Schema coverage is only 50% and the nested entry object leaves type, tag_ids, task_id, billable, project_id, and description entirely undocumented; workspace_id has no description either. The description adds no meaning beyond restating the workspace path segment, so it fails to compensate for the gap.

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 names a specific verb and resource ('Creates a time entry in a workspace') and even pins the REST endpoint, so the action is unambiguous. It does not, however, distinguish itself from update_time_entry or list_time_entries beyond the verb difference, which keeps it short of a 5.

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 when-to-use guidance is given: nothing says whether this is for manual backfill versus stopping a running timer, nor which sibling to choose instead. The endpoint string is background, not usage guidance.

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

Deploy Server

Other Tools