Skip to main content
Glama
impure0xntk

Wakapi MCP Server

by impure0xntk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get All Time Since Today

get_all_time_since_today

Retrieve a user's all-time coding summary up to today, including total time, to analyze development activity in Wakapi.

Instructions

Retrieve summary for all time since today for the specified user.

operationId: get-all-time summary: Retrieve summary for all time description: Mimics https://wakatime.com/developers#all_time_since_today tags: [wakatime] parameters:

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNocurrent

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesModel for all time data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / user / title
      Removed value: -"User"
    • removedOutput schema / $defs
      Removed value: -{
-  "AllTimeData": {
-    "description": "Model for all time data.",
-    "properties": {
-      "is_up_to_date": {
-        "title": "Is Up To Date",
-        "type": "boolean"
-      },
-      "range": {
-        "$ref": "#/$defs/AllTimeRange"
-      },
-      "text": {
-        "title": "Text",
-        "type": "string"
-      },
-      "total_seconds": {
-        "title": "Total Seconds",
-        "type": "number"
-      }
-    },
-    "required": [
-      "total_seconds",
-      "text",
-      "is_up_to_date",
-      "range"
-    ],
-    "title": "AllTimeData",
-    "type": "object"
-  },
-  "AllTimeRange": {
-    "description": "Model for all time range.",
-    "properties": {
-      "end": {
-        "title": "End",
-        "type": "string"
-      },
-      "end_date": {
-        "title": "End Date",
-        "type": "string"
-      },
-      "start": {
-        "title": "Start",
-        "type": "string"
-      },
-      "start_date": {
-        "title": "Start Date",
-        "type": "string"
-      },
-      "timezone": {
-        "title": "Timezone",
-        "type": "string"
-      }
-    },
-    "required": [
-      "start",
-      "start_date",
-      "end",
-      "end_date",
-      "timezone"
-    ],
-    "title": "AllTimeRange",
-    "type": "object"
-  }
-}
    • removedOutput schema / properties / data / $ref
      Removed value: -"#/$defs/AllTimeData"
    • addedOutput schema / properties / data / description
      Added value: +"Model for all time data."
    • addedOutput schema / properties / data / properties
      Added value: +{
+  "is_up_to_date": {
+    "type": "boolean"
+  },
+  "range": {
+    "description": "Model for all time range.",
+    "properties": {
+      "end": {
+        "type": "string"
+      },
+      "end_date": {
+        "type": "string"
+      },
+      "start": {
+        "type": "string"
+      },
+      "start_date": {
+        "type": "string"
+      },
+      "timezone": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "start",
+      "start_date",
+      "end",
+      "end_date",
+      "timezone"
+    ],
+    "type": "object"
+  },
+  "text": {
+    "type": "string"
+  },
+  "total_seconds": {
+    "type": "number"
+  }
+}
    • addedOutput schema / properties / data / required
      Added value: +[
+  "total_seconds",
+  "text",
+  "is_up_to_date",
+  "range"
+]
    • addedOutput schema / properties / data / type
      Added value: +"object"
    • removedOutput schema / title
      Removed value: -"AllTimeViewModel"
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses the authentication requirement (ApiKeyAuth with Base64 Basic header) and the response schema name, but it does not explicitly state that the operation is read-only or describe rate limits or side effects.

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 description is bloated with raw OpenAPI YAML including operationId, tags, and response details. The useful information is not front-loaded or structured for quick selection, and much of the embedded metadata is irrelevant to invocation.

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?

For a simple one-parameter tool with an output schema, the description covers authentication and response type. It remains incomplete because it omits usage context, contradicts the schema on required/default status, and does not clarify what 'all time since today' returns beyond a schema reference.

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 0%, so the description must compensate. It does mention the user parameter can be an ID or 'current', which adds some meaning. However, it also states the parameter is required, while the actual input schema has no required parameters and sets a default of 'current'; this contradiction could mislead an agent.

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 first sentence states a specific verb and resource: retrieve a summary of all time since today for a user. It clearly identifies the operation, though it does not differentiate from siblings like get_stats or get_recent_logs.

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?

The description gives no guidance on when to use this tool versus alternatives such as get_stats or get_recent_logs. It only restates the purpose and provides an API documentation link, leaving the agent to infer usage from the name alone.

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

Deploy Server

Other Tools