Wakapi MCP Server

Get Recent Logs

get_recent_logs

Retrieve recent coding activity logs (heartbeats) for a user over multiple days. Filter by project and set limits to analyze development time.

Instructions

Get heartbeats of user for recent days (extension of heartbeats GET).

Mimics https://wakatime.com/api/v1/users/{user}/heartbeats for multiple days.

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Number of days to retrieve.
`user`	No	Username (or current).	current
`limit`	No	Maximum number of heartbeats.
`project_name`	No	Filter by project.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.2.0Oct 7, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / days / description
```
Added value: +"Number of days to retrieve."
```
- removedInput schema / properties / days / title
```
Removed value: -"Days"
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum number of heartbeats."
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- addedInput schema / properties / project_name / description
```
Added value: +"Filter by project."
```
- removedInput schema / properties / project_name / title
```
Removed value: -"Project Name"
```
- addedInput schema / properties / user / description
```
Added value: +"Username (or current)."
```
- removedInput schema / properties / user / title
```
Removed value: -"User"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / title
```
Removed value: -"_WrappedResult"
```
First observedOct 4, 2025

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description must carry behavioral context, and it usefully discloses that ApiKeyAuth is required with a Base64-encoded API key in the Authorization header. It also implies a read operation via 'Get' and 'mimics ... heartbeats GET,' but it does not cover rate limits, pagination, or safety profile beyond the auth requirement.

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?

The description is three sentences and front-loads the core purpose before giving the API mimicry and authentication detail. The second sentence is slightly redundant with the first, but overall it is efficient and well-structured.

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?

Given four optional parameters, no annotations, and an existing output schema, the description covers the essential purpose and authentication requirement. It does not need to explain return values, but it could be more complete by addressing when to prefer this over sibling tools.

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?

The input schema has 100% description coverage for all four parameters, so the schema already documents days, user, limit, and project_name clearly. The description adds no parameter-level meaning beyond what the schema provides, making the baseline score of 3 appropriate.

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 states a specific verb and resource: 'Get heartbeats of user for recent days,' and clarifies it is an extension of the heartbeats GET for multiple days. It distinguishes itself from siblings like get_stats by focusing on raw heartbeats, though it does not explicitly contrast with those siblings.

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?

Usage is implied by 'extension of heartbeats GET' and 'for multiple days,' suggesting it should be used when multi-day heartbeat data is needed. However, there is no explicit guidance on when to use this tool versus alternatives like get_stats or get_all_time_since_today, and no exclusions are stated.

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

Deploy Server