Skip to main content
Glama

Timix.AI

by ai.timix
OverviewDiscussionsAdmin

log_time

Create a single time entry on a subtask for the current user. Requires permission to log time.

Input Schema

NameRequiredDescriptionDefault
dateYesDate of the work (ISO 8601 format, e.g. 2026-01-15).
textNoOptional description of the work performed.
hoursYesNumber of hours worked (greater than 0 and at most 24).
start_timeNoOptional start time of day in 24-hour HH:mm (e.g. "12:00"). Set this when the user gives a specific time or a time range (and put the range length in 'hours'); the entry then runs from this time for 'hours'. When omitted, the entry starts right after the user's last entry that day, counting entries on cards still waiting for confirmation (09:00 on a day with nothing logged). To change a card that is still waiting for confirmation, propose its change in full (every entry it holds, each at the start_time it has there; a batch card with bulk_create_time_reports) and tell the user to cancel the old card.
subtask_idYesId of the subtask to log time against. All time entries are recorded at the subtask level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / start_time / description
      Previous value: -"Optional start time of day in 24-hour HH:mm (e.g. \"12:00\"). Set this when the user gives a specific time or a time range (and put the range length in 'hours'); the entry then runs from this time for 'hours'. When omitted, the entry starts right after the user's last entry that day, counting entries on cards still waiting for confirmation (09:00 on a day with nothing logged). To correct a card that is still waiting for confirmation, pass that card's start_time."New value: +"Optional start time of day in 24-hour HH:mm (e.g. \"12:00\"). Set this when the user gives a specific time or a time range (and put the range length in 'hours'); the entry then runs from this time for 'hours'. When omitted, the entry starts right after the user's last entry that day, counting entries on cards still waiting for confirmation (09:00 on a day with nothing logged). To change a card that is still waiting for confirmation, propose its change in full (every entry it holds, each at the start_time it has there; a batch card with bulk_create_time_reports) and tell the user to cancel the old card."
  2. Changed1 schema field changed
    • changedInput schema / properties / start_time / description
      Previous value: -"Optional start time of day in 24-hour HH:mm (e.g. \"12:00\"). Set this when the user gives a specific time or a time range (and put the range length in 'hours'); the entry then runs from this time for 'hours'. Defaults to 09:00 when omitted."New value: +"Optional start time of day in 24-hour HH:mm (e.g. \"12:00\"). Set this when the user gives a specific time or a time range (and put the range length in 'hours'); the entry then runs from this time for 'hours'. When omitted, the entry starts right after the user's last entry that day, counting entries on cards still waiting for confirmation (09:00 on a day with nothing logged). To correct a card that is still waiting for confirmation, pass that card's start_time."
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the permission prerequisite. It still omits what happens to adjacent entries, whether the write is reversible, and the auto-sequencing behavior that lives only in the schema's start_time note.

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, purpose front-loaded, prerequisite second. Nothing is wasted or buried.

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?

For a five-parameter mutation with no annotations and no output schema, the description is thin: it covers only purpose and permission while the substantive behavior (entry placement, day sequencing, card-confirmation handling) is left to the schema text.

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 all five parameters are already documented in the schema, including the detailed start_time sequencing rules. The description adds no parameter meaning beyond that, making the baseline 3 appropriate.

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 ("Create a single time entry") and pins the scope to a subtask for the current user. The word "single" implicitly distinguishes it from the bulk variants, though no sibling is named explicitly.

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?

It gives one prerequisite ("Requires permission to log time"), which is real usage guidance. However it never says when to prefer this over create_time_report, bulk_create_time_reports, or start_timer, leaving the agent to infer from the word "single".

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

All Timix.AI toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources