Skip to main content
Glama

list-team-holidays

Retrieve team holidays with filters for department, date range, status, and type. Supports pagination for large datasets.

Instructions

List all team holidays with optional filtering by department, date range, or active status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
department_idNoFilter by department ID
region_idNoFilter by region ID
start_dateNoFilter holidays starting from this date (YYYY-MM-DD)
end_dateNoFilter holidays ending before this date (YYYY-MM-DD)
activeNoFilter by active status (0=inactive, 1=active)
recurringNoFilter by recurring status (0=one-time, 1=recurring)
holiday_typeNoFilter by holiday type (0=full day, 1=partial day)
pageNoPage number for pagination
per-pageNoNumber of items per page (max 200)
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits such as pagination, response format, or default behavior when no filters are applied. It only mentions optional filtering, omitting important details.

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 a single clear sentence with no redundancy. However, it could be slightly expanded to include pagination or response details without losing conciseness.

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?

Given 9 optional parameters and no output schema, the description is too minimal. It does not explain pagination, when to use filters, or what the response contains, making it incomplete for complex usage.

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 each parameter is already described. The description repeats some filters (department, date range, active) but adds no new meaning beyond the schema. 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?

The description clearly states it lists all team holidays with optional filtering. However, it does not distinguish this general list from specialized sibling tools like list-team-holidays-by-date-range and list-team-holidays-by-department.

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 is provided on when to use this tool versus its specialized siblings. The description does not mention alternatives or contexts that favor one over the others.

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/asachs01/float-mcp'

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