Wakapi MCP Server

Get User

get_user

Retrieve Wakapi user details and coding stats by ID or 'current'. Requires API key authentication.

Instructions

Retrieve the given user.

operationId: get-wakatime-user summary: Retrieve the given user description: Mimics https://wakatime.com/developers#users tags: [wakatime] parameters:

name: user in: path description: User ID to fetch (or 'current') required: true schema: type: string responses: 200: description: OK schema: v1.UserViewModel

Requires ApiKeyAuth: Set header Authorization to your API Key encoded as Base64 and prefixed with Basic.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user`	No		current

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	Model for user.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.2.0Oct 7, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / user / title
```
Removed value: -"User"
```

removedOutput schema / $defs

Removed value: -{
-  "User": {
-    "description": "Model for user.",
-    "properties": {
-      "created_at": {
-        "title": "Created At",
-        "type": "string"
-      },
-      "display_name": {
-        "title": "Display Name",
-        "type": "string"
-      },
-      "email": {
-        "title": "Email",
-        "type": "string"
-      },
-      "full_name": {
-        "title": "Full Name",
-        "type": "string"
-      },
-      "id": {
-        "title": "Id",
-        "type": "string"
-      },
-      "is_email_confirmed": {
-        "title": "Is Email Confirmed",
-        "type": "boolean"
-      },
-      "is_email_public": {
-        "title": "Is Email Public",
-        "type": "boolean"
-      },
-      "last_heartbeat_at": {
-        "title": "Last Heartbeat At",
-        "type": "string"
-      },
-      "last_plugin_name": {
-        "title": "Last Plugin Name",
-        "type": "string"
-      },
-      "last_project": {
-        "title": "Last Project",
-        "type": "string"
-      },
-      "modified_at": {
-        "title": "Modified At",
-        "type": "string"
-      },
-      "photo": {
-        "title": "Photo",
-        "type": "string"
-      },
-      "timezone": {
-        "title": "Timezone",
-        "type": "string"
-      },
-      "username": {
-        "title": "Username",
-        "type": "string"
-      },
-      "website": {
-        "title": "Website",
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "username",
-      "display_name",
-      "full_name",
-      "email",
-      "photo",
-      "website",
-      "timezone",
-      "created_at",
-      "modified_at",
-      "last_heartbeat_at",
-      "last_plugin_name",
-      "last_project",
-      "is_email_confirmed",
-      "is_email_public"
-    ],
-    "title": "User",
-    "type": "object"
-  }
-}

removedOutput schema / properties / data / $ref
```
Removed value: -"#/$defs/User"
```
addedOutput schema / properties / data / description
```
Added value: +"Model for user."
```

addedOutput schema / properties / data / properties

Added value: +{
+  "created_at": {
+    "type": "string"
+  },
+  "display_name": {
+    "type": "string"
+  },
+  "email": {
+    "type": "string"
+  },
+  "full_name": {
+    "type": "string"
+  },
+  "id": {
+    "type": "string"
+  },
+  "is_email_confirmed": {
+    "type": "boolean"
+  },
+  "is_email_public": {
+    "type": "boolean"
+  },
+  "last_heartbeat_at": {
+    "type": "string"
+  },
+  "last_plugin_name": {
+    "type": "string"
+  },
+  "last_project": {
+    "type": "string"
+  },
+  "modified_at": {
+    "type": "string"
+  },
+  "photo": {
+    "type": "string"
+  },
+  "timezone": {
+    "type": "string"
+  },
+  "username": {
+    "type": "string"
+  },
+  "website": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / data / required

Added value: +[
+  "id",
+  "username",
+  "display_name",
+  "full_name",
+  "email",
+  "photo",
+  "website",
+  "timezone",
+  "created_at",
+  "modified_at",
+  "last_heartbeat_at",
+  "last_plugin_name",
+  "last_project",
+  "is_email_confirmed",
+  "is_email_public"
+]

addedOutput schema / properties / data / type
```
Added value: +"object"
```
removedOutput schema / title
```
Removed value: -"UserViewModel"
```

First observedOct 4, 2025

TDQS

C2.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add a genuinely useful behavioral detail: ApiKeyAuth is required, with the header formatted as Base64 Basic auth. However, it discloses nothing about reversibility, rate limits, or error behavior for this read call.

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

Conciseness2/5

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

The text is a raw spec dump mixing prose, YAML, path/parameter blocks, and a response schema reference. It is not front-loaded around the actionable content and includes redundant metadata like operationId and tags that add no invocation value.

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 need not be explained, and auth is covered. For a one-parameter read tool this is roughly sufficient, but the messy structure and absent usage guidance leave the definition thinner than it should be.

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 description coverage is 0%, so the schema text alone gives no meaning for `user`. The description compensates partially by explaining the path parameter is a user ID, or 'current' for the authenticated user, but it does not clarify the default behavior or accepted formats beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the verb and resource ('Retrieve the given user'), so the operation is identifiable, but it offers no differentiation from siblings like get_stats or get_projects. The rest of the text is raw OpenAPI metadata (operationId, tags) rather than purposeful description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use, when-not-to-use, or alternative guidance is given. The only implicit usage cue is the embedded path note that 'current' fetches the authenticated user, but this is not framed as guidance versus using a specific user ID.

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

Deploy Server