kimai-mcp-server

Get Kimai Expense

kimai_get_expense

Read-onlyIdempotent

Fetch a single expense from Kimai by its ID. Returns the expense details in markdown or JSON format for easy viewing or integration.

Instructions

Read one expense from /api/expenses/ when the Kimai expenses feature/plugin is available. This tool is read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Kimai entity ID.
`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

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context about plugin dependency and explicitly states 'This tool is read-only.', reinforcing the safety profile. No 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?

The description is two sentences, each serving a distinct purpose: tool action and prerequisite, then read-only nature. No unnecessary words, front-loaded with the key action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the tool having no output schema, the description does not describe what the response contains or its structure. It only says 'Read one expense', leaving the agent to infer the return format. Given the lack of output schema, this is a significant gap.

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 the schema fully documents both parameters (id and response_format). The description adds no additional meaning or usage guidance for these parameters beyond what is already in the schema.

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

Purpose5/5

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

The description clearly states the verb 'Read', the resource 'one expense', and the API endpoint '/api/expenses/<id>'. It also distinguishes from siblings like kimai_list_expenses by focusing on a single expense.

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

Usage Guidelines4/5

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

The description includes a prerequisite ('when the Kimai expenses feature/plugin is available'), which helps the agent understand when the tool is valid. It implies use for reading a single expense by ID, though it does not explicitly exclude cases like listing expenses.

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