Skip to main content
Glama

Update time entry

update_time_report
DestructiveIdempotent

Update fields on one of your own time entries (PATCH — only the fields you supply are changed; everything else is left as-is). Supply the time_report_id plus any combination of date, start_time, hours, and text.

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": {
      "time_report_id": "<time_report_id>"
    },
    "name": "update_time_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoNew date (ISO 8601 YYYY-MM-DD).
textNoNew description (max 1000 characters).
hoursNoNew duration in hours (> 0 and ≤ 24).
start_timeNoNew start time in 24-h HH:mm.
time_report_idYesId of the time entry to update: the time_report_id list_my_time_entries returns for it.
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / time_report_id / description
      Previous value: -"Id of the time entry to update."New value: +"Id of the time entry to update: the time_report_id list_my_time_entries returns for it."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description adds real behavioral context beyond the annotations: only supplied fields change and everything else is left as-is, plus a scope restriction to the caller's own entries. It does not address the destructiveHint=true implication (e.g., that overwriting hours on a billed entry is irreversible) or any permission requirements, so it stops short of full disclosure.

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, front-loaded with the core action, with the PATCH semantics tucked into a compact parenthetical. Nothing is redundant or wasted.

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 a single-record mutation with no output schema, the definition covers what is changed, what is preserved, and which id to use. It leaves out error/failure behavior and any side effects on billing or approvals, which keeps it from being fully complete.

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 100%, so all six parameters including time_report_id and idempotency_key are already documented. The description restates the four updatable field names and clarifies their optionality, but adds no format or constraint detail beyond the schema — baseline 3 applies.

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 and resource ("Update fields on one of your own time entries") and scopes it to the caller's own entries. The singular framing implicitly separates it from bulk_update_time_reports, but no sibling is named, so an agent must infer that distinction.

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?

The PATCH explanation and "any combination of" guidance make the intended usage pattern clear, and it says the id is required. However, it never states when to prefer bulk_update_time_reports or create_time_report instead, and gives no preconditions such as whether the entry must be unbilled or unapproved.

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