Skip to main content
Glama

Track time

create_time_entry

Records time on a project task: for "track 2 hours on Website", call list_projects first and pass the project_task_id of the task on that project. hours takes a duration (2h, 1:30, 90m, 1.5); spent_on is an ISO date and defaults to today in the time zone of the workspace. The rate and the billable flag come from the project.

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": {
      "project_task_id": "<project_task_id>",
      "hours": "<hours>"
    },
    "name": "create_time_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursYesA duration: `2h`, `1:30`, `90m`, `1.5`, or a number of hours
notesNo
spent_onNoToday of the workspace by default
member_idNoA teammate whose time the token may change; the member of the token by default
project_idNoThe project of the task, when the client chose it: a project task of another project is `other_project`
project_task_idYesA `project_task_id` of a project of `GET /api/v1/projects`

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.1/5.0
Behavior3/5

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

Annotations declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description only needs to add context. It does add useful behavior: rate and billable flag are inherited from the project rather than settable, and spent_on defaults to today in the workspace time zone. It does not warn that repeated calls with the same inputs create separate entries (consistent with idempotentHint=false), which is a meaningful omission for a create operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then the disambiguating example, then parameter notes — a sensible order with no filler. The example phrase is dense but earns its place by showing the natural-language-to-parameter mapping; the only mild redundancy is restating hours formats already hinted in the schema.

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 required parameters are covered well. For a 6-parameter create tool, the remaining gap is the unattributed member_id and project_id semantics, which the schema partially covers but the description does not reinforce.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83%, so the baseline is 3; the description earns an extra point by giving concrete accepted duration syntax (`2h`, `1:30`, `90m`, `1.5`) and clarifying that spent_on defaults to the workspace time zone. It leaves member_id (recording time on behalf of a teammate) and project_id (the other_project case) unexplained even though both carry non-obvious semantics.

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 and resource ('Records time on a project task') and immediately anchors it with a concrete user utterance mapping ('track 2 hours on Website'). This distinguishes it from timer-based siblings like start_timer/stop_timer and from update_time_entry without needing to open any schema.

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 prerequisite workflow: call list_projects first and pass the `project_task_id` of the task on that project, which is exactly the missing link an agent would otherwise stumble on. It does not explicitly exclude alternatives (e.g., use start_timer for live tracking, or update_time_entry to amend an existing entry), so it stops short of full when/when-not 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