Skip to main content
Glama

Wakatime Current User

wakatime_current_user
Read-onlyIdempotent

Profile of the WakaTime account that owns your OAuth token. Requires your own WakaTime personal OAuth token as _apiKey.

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": {},
    "name": "wakatime_current_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.

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 safe read-only, idempotent, open-world, non-destructive behavior. The description adds the important behavioral fact that access requires the caller's own personal WakaTime OAuth token, though it does not discuss rate limits or deeper account-scope behavior.

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 with no wasted wording. The key identity is front-loaded, and the authentication requirement follows immediately.

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 single-parameter, read-only profile endpoint with a full annotation set and an output schema, the description gives enough context to select and call the tool. It could clarify its relationship to public-profile alternatives, but it is largely complete.

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?

There is only one parameter and schema description coverage is 100%, so the schema already explains _apiKey in more detail: required for account data and optional for public profiles/stats. The description restates that the token is required but adds no new syntax, format, or edge-case guidance.

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 the resource precisely: the profile of the WakaTime account that owns the caller's OAuth token. It does not explicitly name or contrast sibling tools such as wakatime_user or wakatime_meta, so sibling differentiation is inferred rather than stated.

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?

Implies usage when the caller needs the token owner's account profile and states the authentication prerequisite. It lacks explicit when-not guidance or a named alternative for public profiles, though the schema notes that _apiKey is optional for public profiles and stats.

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.