Skip to main content
Glama

Wakatime Stats

wakatime_stats
Read-onlyIdempotent

Fetch aggregated WakaTime coding stats for a user over a range ("last_7_days", "last_30_days", "last_6_months", "last_year", "all_time"); returns totals and rankings by language, project, editor, and OS. Keyless for public profiles; pass your OAuth token as _apiKey for private ones.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "range": "last_30_days",
      "user_id": "wakatime_user_123"
    },
    "name": "wakatime_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYes
_apiKeyNoYour WakaTime personal OAuth access token (Bearer). Required for account data (current user, summaries, durations, heartbeats, goals, projects, commits); optional for public profiles and stats.
projectNo
timeoutNo
user_idYes
writes_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds something the annotations do not: the auth model (keyless for public profiles, OAuth bearer token for private accounts), which materially changes how an agent must call it.

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?

Two sentences, front-loaded with the resource and scope, then the auth condition. The range enumeration is dense but earns its place since it is the only source of allowed values; little is wasted.

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?

An output schema exists, so return values are adequately covered by the brief mention of totals and rankings. For a 6-parameter tool at 17% schema coverage, though, the description should account for filters like project and writes_only, and it does not.

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 only 17%, so the description has to compensate, and it partly does: it supplies the accepted range values (the schema itself declares no enum) and clarifies _apiKey's role. It says nothing about project, timeout, or writes_only, leaving half the parameters opaque in both places.

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 ("Fetch aggregated WakaTime coding stats") and enumerates the exact range values plus the dimensions of the result (language, project, editor, OS). That is enough to tell it apart from raw-activity siblings like heartbeats or durations, 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?

The description gives real routing guidance on authentication ("Keyless for public profiles; pass your OAuth token as _apiKey for private ones"), which tells the agent when a token is needed. It stops short of saying when to prefer this aggregated view over per-day or per-project tools, so the when-to-use story is only implied.

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.