Skip to main content
Glama
technogise

keka-mcp

by technogise
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get holidays

get_holidays

Fetch holidays from all Keka holiday calendars, or filter by calendar ID and year. Combines results from multiple calendars into one list.

Instructions

Fetch holidays from Keka's holiday calendar(s). Keka scopes holidays per calendar rather than org-wide, so if 'calendarId' is omitted this tool first looks up every holiday calendar and then fetches and combines holidays from all of them (most tenants only have one). Each returned holiday is tagged with the calendarId/calendarName it came from. Automatically pages through every result set involved and returns it combined.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageSizeNoPage size used internally per request to Keka (max 200, default 100).
calendarIdNoRestrict to a single holiday calendar ID. If omitted, holidays from every calendar are fetched and combined.
calendarYearNoFilter holidays to a specific calendar year (e.g. 2026). Omit to get all years Keka has data for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so exceptionally well. It discloses that multiple calendars are queried and combined, that results are tagged with origin calendar metadata, and that pagination is handled automatically.

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?

Three dense sentences with no filler. The purpose is front-loaded, and each subsequent sentence adds behavior an agent needs to know before calling the tool.

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 scoping, combining, tagging, and pagination, which is strong for a read-style lookup tool with no output schema. It could go further by naming the returned holiday fields, but an agent can invoke the tool correctly with the information given.

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 coverage is 100%, but the description adds meaningful behavioral context beyond the schema, particularly for calendarId omission and automatic pagination. This lifts it above the baseline without fully detailing every parameter's edge behavior.

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 opens with a specific verb and resource: 'Fetch holidays from Keka's holiday calendar(s).' It clearly differentiates itself from sibling tools by explaining the per-calendar scoping behavior rather than an org-wide holiday lookup.

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 context for when to use the tool and how optional parameters change its behavior, especially the calendarId omission path. It does not explicitly name alternatives like get_leaves, so it stops short of full exclusion guidance.

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

Deploy Server

Other Tools