kimai-mcp-server

List Kimai Tasks

kimai_list_tasks

Read-onlyIdempotent

Retrieve a list of tasks from Kimai's /api/tasks endpoint. This read-only tool works when the tasks feature or plugin is active.

Instructions

List tasks from /api/tasks when the Kimai tasks feature/plugin is available. This tool is read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kimai_list_tasks"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Kimai API page number for paginated endpoints.
`size`	No	Kimai API page size. Kimai supports a maximum size of 500.
`response_format`	No	Output format: markdown for human-readable summaries, json for structured output.	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The description explicitly states read-only, which aligns with annotations. It adds the plugin dependency context, but annotations already cover the safety profile (readOnlyHint, destructiveHint). No behavioral contradictions.

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 sentences, front-loaded with key information. Every sentence is necessary and concise.

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?

The description covers the essential purpose and condition (plugin availability). Annotations and schema handle pagination and safety. Lacks description of output fields, but acceptable for a list tool.

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 coverage is 100%, so baseline 3 is appropriate. The description does not add any parameter details beyond what the schema provides.

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 it lists tasks from /api/tasks and is read-only. It clearly identifies the resource and action, but does not differentiate from sibling tools like kimai_list_projects or kimai_list_activities.

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 mentions availability when the tasks plugin is active, but provides no guidance on when to use this tool versus alternatives or when not to use it.

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