Wakatime

Durations

durations

Read-onlyIdempotent

Fetch WakaTime coding durations (start/end timestamps with project and file) for a single day (date required, YYYY-MM-DD); optionally slice_by entity/language/branch for granular session data. Requires your own WakaTime personal OAuth token as _apiKey.

Input Schema

Name	Required	Description
`date`	Yes
`_apiKey`	No	Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.
`project`	No
`timeout`	No
`user_id`	Yes
`branches`	No
`slice_by`	No
`timezone`	No
`writes_only`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / _apiKey

Added value: +{
+  "description": "Your WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.",
+  "type": "string"
+}

First observedMay 26, 2026

TDQS

A4/5.0

Behavior4/5

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

The description adds an important behavioral prerequisite beyond the annotations: a personal WakaTime OAuth token is required as _apiKey. It also describes the return shape as start/end timestamps with project and file. It does not cover rate limits or pagination, but annotations already establish the safe read-only profile.

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?

The description is compact and front-loaded with the core action and resource. Every clause adds useful scope, format, or auth information without unnecessary prose.

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?

The output schema exists, so return values need not be fully explained, and the annotations cover safety. However, for a 9-parameter tool with only 11% schema description coverage, the description leaves too many parameters undocumented, including the required user_id.

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

Parameters2/5

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

Schema description coverage is only 11%, so the description must compensate for many undocumented parameters. It explains date format and slice_by values, but omits the required user_id and several optional parameters such as project, timezone, writes_only, branches, and timeout.

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?

The description uses a specific verb and resource: fetch WakaTime coding durations. It clarifies the scope as a single day and distinguishes the output as start/end timestamps with project and file, which separates it from aggregate siblings like summaries.

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?

It states the primary use case clearly: single-day durations with date required in YYYY-MM-DD format. It also explains when to use slice_by for granular session data. It does not explicitly name alternatives or exclusions, so it falls short of a full 5.

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

All Wakatime tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.