Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

list_public_holidays

Retrieve public holidays by calendar ID and year. Filter results to plan time away or comply with local regulations.

Instructions

List public holidays. Optional filters: calendarId, year.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendar_idNo
yearNo

Implementation Reference

  • The async function that executes the 'list_public_holidays' tool logic. Calls the HumaansClient's list_page method with the '/public-holidays' endpoint, passing optional filters for calendar_id and year.
    @mcp.tool()
    async def list_public_holidays(calendar_id: str | None = None, year: int | None = None) -> Any:
        """List public holidays. Optional filters: calendarId, year."""
        return await client().list_page(
            "/public-holidays",
            filters={"publicHolidayCalendarId": calendar_id, "year": year},
            limit=250,
        )
  • The tool is registered via the @mcp.tool() decorator on the list_public_holidays function, which registers it with the FastMCP server.
    @mcp.tool()
  • The client() helper function (singleton) returns a HumaansClient instance that list_public_holidays calls to make the API request.
    def client() -> HumaansClient:
        global _client
        if _client is None:
            _client = HumaansClient()
        return _client
  • HumaansClient.list_page - the method used by list_public_holidays to fetch paginated data from the API endpoint with filters.
    async def list_page(
        self,
        path: str,
        filters: dict[str, Any] | None = None,
        limit: int = 100,
        skip: int = 0,
    ) -> Any:
        params = dict(filters or {})
        params["$limit"] = limit
        params["$skip"] = skip
        return await self.get(path, params)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only describes a read operation but lacks details on pagination, rate limits, data scope, or any side effects.

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 very concise with a single sentence that is easy to parse. Could include more information without sacrificing brevity, but it is not overly verbose.

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 the simplicity of the tool (2 optional params, no output schema), the description is minimally adequate but lacks details on return format, error handling, or usage examples.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description says 'Optional filters: calendarId, year' but does not explain what each parameter does or its valid values. Schema coverage is 0%, so description should compensate but is insufficient.

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 the tool lists public holidays with optional filters. While it doesn't explicitly differentiate from sibling tools like list_public_holiday_calendars, the name and context imply distinct resources.

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 over alternatives or any prerequisites. The description only mentions optional filters but does not explain typical use cases or conditions.

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/ptorsten/humaans-mcp'

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