Skip to main content
Glama
jais2402
by jais2402

Update an existing time record

everhour_update_time_record
Idempotent

Modify an existing time record by updating its duration, date, or comment. Uses the record ID from list or log commands.

Instructions

Modify an existing time record (change duration, date, or comment).

Args:

  • record_id (number): The time record ID returned by everhour_list_time_records or everhour_log_time.

  • duration ({ hours? } | { seconds? }, optional): New duration. Omit to keep existing.

  • date (string, optional): New date YYYY-MM-DD. Omit to keep existing.

  • comment (string, optional): New comment. Pass empty string to clear it. Omit to keep existing.

  • response_format ('markdown' | 'json')

Returns the updated time record.

Examples:

  • "Change record 12345 to 3 hours" → record_id=12345, duration={ hours: 3 }

  • "Update the comment on record 12345 to 'pair session with Alex'" → record_id=12345, comment='pair session with Alex'

Error Handling:

  • 404 → record not found

  • 403 → record locked (period closed) or not yours

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
commentNo
durationNo
record_idYesID of the time record to update.
response_formatNoOutput format: 'markdown' for human-readable text or 'json' for machine-readable structured datamarkdown
Behavior4/5

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

Descriptors 'Modify' and error for locked records add context beyond annotations. IdempotentHint is noted but not explained; still sufficient for understanding behavior.

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?

Well-structured with Args, Returns, Examples, Error Handling. Every sentence adds value; no wasted words.

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

Completeness5/5

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

For a 5-param update tool, description covers all aspects: parameter roles, examples, error cases, and return value. No gaps given simplicity of tool.

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?

Despite 40% schema coverage, description fully explains all parameters: record_id source, duration format, date format, comment clearing, response_format options. Examples reinforce usage.

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?

Clearly states 'Modify an existing time record' with specific attributes (duration, date, comment). Distinguishes from sibling tools like delete or log time.

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?

Provides parameter guidance (e.g., record_id source, optional semantics, clearing comment) and error handling for 404/403. Lacks explicit when-not-to-use, but purpose implies it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jais2402/ever-hour-mcp-for-jais'

If you have feedback or need assistance with the MCP directory API, please join our Discord server