Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

list_time_away

Retrieve time-away records by person ID and date range. Filter absenteeism data for specific employees or time periods.

Instructions

List time-away records. Optional filters: personId, startDate, endDate (YYYY-MM-DD).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idNo
start_dateNo
end_dateNo
limitNo
skipNo

Implementation Reference

  • The tool 'list_time_away' is registered via @mcp.tool() decorator on an async function. It makes an API call to Humaans backend filtering time-away records.
    @mcp.tool()
    async def list_time_away(
        person_id: str | None = None,
        start_date: str | None = None,
        end_date: str | None = None,
        limit: int = 100,
        skip: int = 0,
    ) -> Any:
        """List time-away records. Optional filters: personId, startDate, endDate (YYYY-MM-DD)."""
        return await client().list_page(
            "/time-away",
            filters={"personId": person_id, "startDate": start_date, "endDate": end_date},
            limit=limit,
            skip=skip,
        )
  • Handler function for the 'list_time_away' tool. Accepts optional person_id, start_date, end_date filters and pagination (limit/skip). Calls client().list_page('/time-away', ...).
    async def list_time_away(
        person_id: str | None = None,
        start_date: str | None = None,
        end_date: str | None = None,
        limit: int = 100,
        skip: int = 0,
    ) -> Any:
        """List time-away records. Optional filters: personId, startDate, endDate (YYYY-MM-DD)."""
        return await client().list_page(
            "/time-away",
            filters={"personId": person_id, "startDate": start_date, "endDate": end_date},
            limit=limit,
            skip=skip,
        )
  • Input schema/parameters for list_time_away: person_id (str|None), start_date (str|None), end_date (str|None), limit (int, default 100), skip (int, default 0). Output type is Any.
        person_id: str | None = None,
        start_date: str | None = None,
        end_date: str | None = None,
        limit: int = 100,
        skip: int = 0,
    ) -> Any:
Behavior2/5

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

With no annotations, the description must convey behavioral traits. It indicates a read operation but omits details on pagination, default ordering, or behavior for empty results. The 'limit' and 'skip' parameters are not mentioned in the description.

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 concise sentence that front-loads the core action. It could be slightly more structured but is efficient and avoids fluff.

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 lack of output schema and annotations, and five parameters, the description is insufficient. It does not explain filtering semantics (e.g., date range inclusivity), pagination behavior, or the format of returned records, leaving the agent with significant gaps.

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?

The description adds partial meaning by naming three filters (personId, startDate, endDate) and specifying the date format (YYYY-MM-DD), which is not present in the schema (which only has titles). However, it does not cover the 'limit' and 'skip' parameters, and the schema itself has 0% description coverage.

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 action 'List time-away records' and identifies the resource. It is specific and distinguishes from siblings like get_time_away (singular) and list_time_away_allocations, though it does not explicitly contrast with them.

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 sibling tools (e.g., get_time_away, list_time_away_allocations). The description only lists optional filters without indicating context or exclusions.

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