InstaClock

Update time entry

update_time_entry

DestructiveIdempotent

Change the start time, end time or activity of an existing time entry. Passing only endTime for the running entry stops it.

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": {
      "id": "<id>"
    },
    "name": "update_time_entry"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Time entry id
`endTime`	No	ISO 8601 with an offset (2026-10-12T14:30:00+05:30), a local time (2026-10-12 14:30) in your timezone, or "now"
`startTime`	No	ISO 8601 with an offset (2026-10-12T14:30:00+05:30), a local time (2026-10-12 14:30) in your timezone, or "now"
`activityId`	No	Activity id from list_activities
`activityName`	No	Activity name, when the id is not known. Case-insensitive; prefix matches work.

Output Schema

Name	Required	Description	Default
`timezone`	Yes	The user's IANA timezone. Times in this result are in this zone.
`timeEntry`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already disclose that this is a non-read-only, destructive, idempotent operation, so the safety profile is covered. The description adds one genuinely behavioral fact beyond the annotations – the endTime-only call stops a running entry – but says nothing about overwriting existing values, reversibility, or permission requirements.

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?

Two short sentences with no filler; the primary purpose is front-loaded and the special case follows as a secondary clause. Every sentence carries information the agent can act on.

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?

With an output schema present, the description does not need to explain return values, and the annotations cover the mutation profile. Still missing for a destructive update are the interaction with stop_timer, validation rules such as start after end, and what happens to unspecified fields.

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%, so the accepted time formats and the activityId/activityName lookup pattern are already fully documented. The description only enumerates which fields can change and adds no syntax or constraint information beyond the schema, making the baseline 3 correct.

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 states a specific verb and resource ('Change ... an existing time entry') and names the mutable fields, which is enough to separate it from create/log/delete siblings. It stops short of cleanly distinguishing it from stop_timer, since stopping a running entry is described here as a side effect.

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?

There is one implicit usage rule ('Passing only endTime for the running entry stops it'), which tells the agent a conditional case. There is no explicit guidance on when to use this versus stop_timer or log_time_entry, and no preconditions or exclusions are stated.

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

All InstaClock tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?