Skip to main content
Glama

List Recent Kimai Timesheets

kimai_list_recent_timesheets
Read-onlyIdempotent

Retrieve recent timesheet entries from the Kimai API. Use this read-only tool to view recent logged time.

Instructions

List recent Kimai timesheet entries from /api/timesheets/recent. This tool is read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoKimai API page number for paginated endpoints.
sizeNoKimai API page size. Kimai supports a maximum size of 500.
response_formatNoOutput format: markdown for human-readable summaries, json for structured output.markdown
Behavior3/5

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

Annotations already declare readOnlyHint and other safety hints. Description adds the API endpoint path and confirms read-only nature, which is consistent. No new behavioral details beyond annotations.

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 succinct sentences, front-loaded with the action and resource. No extraneous information, highly efficient.

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?

Missing context about what 'recent' means (time period, ordering). No description of return format or pagination behavior. With no output schema, more explanation is needed 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?

All parameters are fully documented in the schema (100% coverage). Description does not add any parameter-level meaning beyond what schema provides, so baseline of 3 is 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?

Clear verb 'List' and resource 'recent timesheet entries', with specific API endpoint path. No explicit differentiation from sibling list tools, but purpose is well-defined.

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?

No guidance on when to use this tool versus other timesheet listing tools like kimai_list_timesheets or kimai_list_active_timesheets. Context of 'recent' is not clarified.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NightSquawk/kimai-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server