Skip to main content
Glama
huebnermarketing

keka-mcp-server

Get Keka Attendance Records

keka_get_attendance
Read-onlyIdempotent

Retrieve employee attendance records including clock-in/out times, total hours, shift, and status for a specified date range or employee list.

Instructions

Retrieve attendance records for employees from Keka.

The Keka API supports a maximum date range of 90 days per request and defaults to the last 30 days.

Args:

  • employeeIds (string, optional): Comma-separated employee IDs to filter records

  • from (string, optional): Start date in ISO 8601 format (e.g., '2025-03-01'). Max 90-day range.

  • to (string, optional): End date in ISO 8601 format (e.g., '2025-03-31'). Max 90-day range.

  • pageNumber (integer): Page number (default: 1)

  • pageSize (integer): Results per page, max 200 (default: 100)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Attendance records per employee per day — clock-in, clock-out, total hours, shift, and status (Present, Absent, Half-Day, etc.).

Examples:

  • View attendance for a team this month → from='2025-03-01', to='2025-03-31', employeeIds='id1,id2'

  • Check if an employee was present → employeeIds='emp123', from='2025-03-10', to='2025-03-10'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd date ISO 8601 (e.g., '2025-03-31'). Max range: 90 days.
fromNoStart date ISO 8601 (e.g., '2025-03-01'). Max range: 90 days.
pageSizeNoResults per page (max 200)
pageNumberNoPage number (starts at 1)
employeeIdsNoComma-separated Keka employee IDs
response_formatNoOutput format: 'markdown' for human-readable, 'json' for machine-readablemarkdown

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, and non-destructive, so the bar for behavioral disclosure is lower. The description adds valuable behavioral details beyond the annotations: the API's 90-day range limit, default to the last 30 days, pagination parameters, and output format selection. No contradiction exists between the description and annotations.

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 well-structured with an opening purpose, API limit note, bullet-style Args list, Returns summary, and Examples. It is longer than the minimum but each section earns its place; slight redundancy exists in repeating the 90-day limit in both prose and the Args list.

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

Completeness5/5

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

For a tool with no output schema, the description compensates by summarizing the return structure and key fields. It covers defaults, constraints, parameter usage, and examples, giving an agent everything needed to invoke the tool correctly and interpret results.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining how to combine parameters (e.g., date ranges and employee IDs) and illustrating with concrete examples. It also mentions the default date window and response_format options, enriching the agent's understanding.

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 states a specific verb ('Retrieve') and resource ('attandance records for employees from Keka'), and further clarifies the returned data (clock-in, clock-out, total hours, shift, status). This clearly distinguishes it from sibling tools that list leave types, employees, or pay groups.

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 provides clear usage context with examples, such as viewing attendance for a team this month or checking a specific employee's presence on a given day. It also notes the default 30-day window and maximum 90-day range, which guides correct invocation. It does not explicitly name alternative tools or exclusion criteria, so it stops short of a perfect score.

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

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/huebnermarketing/keka-mcp'

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