Skip to main content
Glama

Wakatime User

wakatime_user
Read-onlyIdempotent

Public WakaTime profile for a user_id/username; keyless for public profiles, pass your OAuth token as _apiKey for your own or 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": {
      "user_id": "wakatime_user_123"
    },
    "name": "wakatime_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
_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.
user_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the description rightly focuses on the auth model. It adds real behavioral value by spelling out that public access is keyless while private/own data requires a token, which the annotations do not convey.

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?

A single front-loaded sentence covering resource and auth modes with no filler. The semicolon-condensed phrasing is dense but still readable, and nothing needs to be cut.

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?

For a two-parameter read-only lookup with an output schema and full annotations, the description covers what the tool returns (a profile), who can call it, and how auth works. The only meaningful omission is the sibling-routing guidance.

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 only 50%, and user_id has no schema description; the description compensates by stating that it accepts a user_id or a username. It also reinforces how _apiKey is used, matching the schema's Bearer-token wording without contradicting it.

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 names a specific verb and resource ('Public WakaTime profile for a user_id/username') and is immediately distinguishable from generic data endpoints. It stops short of explicitly contrasting itself with the closely named sibling wakatime_current_user, leaving the agent to infer the difference.

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 explicit conditional guidance on credentials: keyless for public profiles, OAuth token for your own or private ones. However, it never tells the agent when to pick this over wakatime_current_user or wakatime_stats, which is the main routing decision an agent faces.

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.