Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

list_public_holiday_calendars

Retrieve all public holiday calendars configured in Humaans. Use this to view available holiday schedules for planning.

Instructions

List all configured public holiday calendars.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that defines the 'list_public_holiday_calendars' MCP tool. It calls the Humaans API at '/public-holiday-calendars' with a limit of 250, returning a paginated list of public holiday calendars.
    @mcp.tool()
    async def list_public_holiday_calendars() -> Any:
        """List all configured public holiday calendars."""
        return await client().list_page("/public-holiday-calendars", limit=250)
  • The tool is registered via the @mcp.tool() decorator from FastMCP, which binds the async function to the MCP server.
    @mcp.tool()
  • Helper method 'list_page' on HumaansClient that constructs query parameters with $limit and $skip and calls the GET endpoint. Used by the handler to fetch the paginated list.
    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)
  • Underlying 'get' method on HumaansClient that performs the actual HTTP GET request to the Humaans API with authorization headers.
    async def get(self, path: str, params: dict[str, Any] | None = None) -> Any:
        clean = {k: v for k, v in (params or {}).items() if v is not None}
        resp = await self._client.get(path, params=clean)
        if resp.status_code >= 400:
            try:
                body = resp.json()
            except Exception:
                body = resp.text
            raise HumaansError(resp.status_code, path, body)
        return resp.json()
Behavior2/5

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

No annotations provided, so the description must carry full behavioral burden. It only says 'list all configured public holiday calendars' without mentioning permissions, side effects, or response details.

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?

A single, clear sentence with no wasted words, appropriately front-loaded.

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

Completeness3/5

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

Adequate for a simple list tool, but lacks details about the output format or any non-obvious behavior. With no output schema, the description should hint at what fields each calendar object contains.

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?

No parameters exist; schema coverage is 100%. With zero params, baseline is 4, and the description adds no param info.

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 clearly states the verb 'list' and the resource 'configured public holiday calendars', distinguishing it from sibling tools like list_public_holidays.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. For a simple list tool, usage is implied but not stated, which is a minor gap.

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