Skip to main content
Glama
impure0xntk

Wakapi MCP Server

by impure0xntk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Projects

get_projects

Retrieve and filter a Wakapi user's projects by keyword to analyze coding time and productivity per project.

Instructions

Retrieve and filter the user's projects.

operationId: get-wakatime-projects summary: Retrieve and filter the user's projects description: Mimics https://wakatime.com/developers#projects tags: [wakatime] parameters:

  • name: user in: path description: User ID to fetch data for (or 'current') required: true schema: type: string

  • name: q in: query description: Query to filter projects by schema: type: string responses: 200: description: OK schema: v1.ProjectsViewModel

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo
userNocurrent

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / q / title
      Removed value: -"Q"
    • removedInput schema / properties / user / title
      Removed value: -"User"
    • removedOutput schema / $defs
      Removed value: -{
-  "Project": {
-    "description": "Model for project.",
-    "properties": {
-      "created_at": {
-        "title": "Created At",
-        "type": "string"
-      },
-      "human_readable_last_heartbeat_at": {
-        "title": "Human Readable Last Heartbeat At",
-        "type": "string"
-      },
-      "id": {
-        "title": "Id",
-        "type": "string"
-      },
-      "last_heartbeat_at": {
-        "title": "Last Heartbeat At",
-        "type": "string"
-      },
-      "name": {
-        "title": "Name",
-        "type": "string"
-      },
-      "urlencoded_name": {
-        "title": "Urlencoded Name",
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "name",
-      "urlencoded_name",
-      "created_at",
-      "last_heartbeat_at",
-      "human_readable_last_heartbeat_at"
-    ],
-    "title": "Project",
-    "type": "object"
-  }
-}
    • removedOutput schema / properties / data / items / $ref
      Removed value: -"#/$defs/Project"
    • addedOutput schema / properties / data / items / description
      Added value: +"Model for project."
    • addedOutput schema / properties / data / items / properties
      Added value: +{
+  "created_at": {
+    "type": "string"
+  },
+  "human_readable_last_heartbeat_at": {
+    "type": "string"
+  },
+  "id": {
+    "type": "string"
+  },
+  "last_heartbeat_at": {
+    "type": "string"
+  },
+  "name": {
+    "type": "string"
+  },
+  "urlencoded_name": {
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / data / items / required
      Added value: +[
+  "id",
+  "name",
+  "urlencoded_name",
+  "created_at",
+  "last_heartbeat_at",
+  "human_readable_last_heartbeat_at"
+]
    • addedOutput schema / properties / data / items / type
      Added value: +"object"
    • removedOutput schema / properties / data / title
      Removed value: -"Data"
    • removedOutput schema / title
      Removed value: -"ProjectsViewModel"
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the ApiKeyAuth requirement and header encoding, and 'Retrieve' implies a read operation, but it does not explain rate limits, pagination, filtering semantics, or what happens when no projects match.

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 useful first sentence is front-loaded, but the rest is an OpenAPI/YAML dump including operationId, tags, responses, and summary. Much of this is redundant or irrelevant to an AI agent selecting and invoking the tool, making the definition unnecessarily bloated.

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?

The description covers auth and both parameters, and an output schema exists so return values need not be explained. However, it lacks usage guidance relative to siblings like get_project_detail, leaving a meaningful gap for a list/filter tool.

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 description coverage is 0%, so the description must compensate. It does provide meaning for both parameters: 'user' is described as the user ID or 'current', and 'q' as a query to filter projects by. The q description remains vague about syntax, but the core semantics are present.

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 clearly states the verb and resource: 'Retrieve and filter the user's projects.' It is specific enough to distinguish this from generic data retrieval, but it does not explicitly differentiate itself from the sibling tool get_project_detail or explain list-versus-detail scope.

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?

There is no explicit guidance on when to use this tool versus alternatives such as get_project_detail. The only implied usage is filtering by the q parameter, but no conditions, exclusions, or alternatives are provided.

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