Skip to main content
Glama

Change a time entry

update_time_entry
Idempotent

Changes the hours, notes, spent_on or project_task_id of a time entry by id; only the given fields change. An entry on an issued invoice, approved, submitted, written off or billed elsewhere is locked.

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

NameRequiredDescriptionDefault
idYesThe id of the entry
hoursNo
notesNo
spent_onNo
project_idNoThe project of the task, when the client chose it: a project task of another project is `other_project`
project_task_idNo

Output Schema

NameRequiredDescriptionDefault
idYes
costNo
hoursYesDecimal hours, such as `1.50`
notesNo
stateYes
amountNo
task_idNo
billableNo
currencyNo
spent_onYes
client_idYes
cost_rateNo
member_idYes
task_nameNo
invoice_idNo
project_idYes
updated_atNo
client_nameNo
hourly_rateNo
inserted_atNo
member_nameNo
project_nameNo
cost_currencyNo
invoice_numberNo
project_task_idYes
billed_elsewhere_onNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations it discloses two real behavioral traits: this is a partial update ('only the given fields change') and it fails against a defined set of locked entry states. The idempotent/read-only/destructive profile is already in the annotations, so credit rests on the locking rule, which materially affects call planning.

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 sentences, zero padding. The mutable-field list and the partial-update semantics come first, and the failure precondition follows immediately.

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?

An output schema exists, so return values need no explanation, and the description covers mutation semantics and the main failure mode. The remaining gap is the unmentioned `project_id` parameter and any permission/auth expectations for a write operation.

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 coverage is low (33%), so the description has to compensate. It clarifies the mutable field set but silently omits `project_id`, which is a valid input in the schema and whose own schema text ('when the client chose it... other_project') is opaque; an agent could reasonably assume project is not updatable. No format or type guidance is added for `hours`, `notes`, or `spent_on`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (changes) plus resource (a time entry) and enumerates exactly which fields are mutable, keyed by `id`. Combined with the sibling set (create/delete/get/list_time_entry), an agent can immediately tell this apart from the other entry tools.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-not condition: entries on an issued invoice, approved, submitted, written off or billed elsewhere are `locked`, which tells the agent when the call will not succeed. It does not name an alternative path for locked entries (e.g. an uninvoiced/reopen route) or point at delete_time_entry for removal, so it stops just short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources