Skip to main content
Glama
pfaeffli

clockodo-mcp-server

by pfaeffli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

edit_my_time_entry

DestructiveIdempotent

Update an existing Clockodo time entry's start/end times, description, customer, service, project, or billable status. Only the fields you specify are changed.

Instructions

Edit one of your time entries. Only the fields you pass are changed.

Pass at least one field.

Args: entry_id: ID of the entry to edit time_since: New start time: local Europe/Zurich time or any ISO 8601 with offset (sent to Clockodo as UTC), e.g. 2025-01-01T09:00:00 time_until: New end time, same format as time_since text: New description customers_id: New customer ID services_id: New service ID projects_id: New project ID billable: 0 = not billable, 1 = billable, 2 = already billed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNo
billableNo
entry_idYes
time_sinceNo
time_untilNo
projects_idNo
services_idNo
customers_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.8.0
    • addedInput schema / properties / billable
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Billable"
+}
    • addedInput schema / properties / customers_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Customers Id"
+}
    • removedInput schema / properties / data
      Removed value: -{
-  "additionalProperties": true,
-  "title": "Data",
-  "type": "object"
-}
    • addedInput schema / properties / projects_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Projects Id"
+}
    • addedInput schema / properties / services_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Services Id"
+}
    • addedInput schema / properties / text
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Text"
+}
    • addedInput schema / properties / time_since
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Time Since"
+}
    • addedInput schema / properties / time_until
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Time Until"
+}
    • changedInput schema / required
      Previous value: -[
-  "entry_id",
-  "data"
-]New value: +[
+  "entry_id"
+]
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true, openWorldHint=true), and the description adds substantive context beyond them: partial-update semantics and the timezone contract that local Europe/Zurich times or ISO 8601 with offset are converted to UTC before being sent. It still does not say what gets destroyed or what happens when editing an already-billed entry, so it is not exhaustive.

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?

Front-loaded with purpose and the partial-update rule, then a compact Args list that earns its space by adding semantics the schema lacks. Slightly list-heavy, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation tool with 0% schema coverage, no output schema, and a destructive hint, the description covers the parameters and the timezone behavior well. Remaining gaps are secondary: failure behavior, permission requirements, and any restrictions on editing billed or locked entries.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does so: every one of the 8 parameters is documented, including the non-obvious billable codes (0/1/2 = not billable/billable/already billed) and the accepted time formats for time_since/time_until. The format and unit details go well beyond the bare schema types.

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?

States a specific verb+resource ('Edit one of your time entries') and immediately clarifies the partial-update semantics ('Only the fields you pass are changed'). It does not explicitly name sibling alternatives like delete_my_time_entry, but the add/edit/delete distinction is unambiguous from the name and opening sentence.

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?

Provides a real precondition ('Pass at least one field'), which prevents the common mistake of calling a no-op edit. However, it offers no when-to-use guidance relative to siblings (e.g., delete_my_time_entry for removal, or when to prefer add_my_time_entry), so usage is only implied.

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