Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

get_time_away

Retrieve a single time-away record by its unique ID to view details of an employee's absence.

Instructions

Retrieve a single time-away record by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
time_away_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual tool handler for 'get_time_away'. It is decorated with @mcp.tool(), takes a time_away_id parameter, and calls the HumaansClient.get() method to retrieve a single time-away record by ID.
    @mcp.tool()
    async def get_time_away(time_away_id: str) -> dict[str, Any]:
        """Retrieve a single time-away record by id."""
        return await client().get(f"/time-away/{time_away_id}")
  • The @mcp.tool() decorator registers 'get_time_away' as a tool on the FastMCP instance named 'mcp' (line 7).
    @mcp.tool()
  • The function signature defines the input schema: a required 'time_away_id' string parameter. The return type is dict[str, Any].
    async def get_time_away(time_away_id: str) -> dict[str, Any]:
  • The HumaansClient.get() helper method is used by the handler to make the actual HTTP GET request to the Humaans API.
    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 description carries full burden. Only states retrieval by id; no disclosure of permissions, error handling, or behavior when record not found.

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?

Single sentence is concise and front-loaded. However, it could be slightly improved with minor context without sacrifice.

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?

Given the tool's simplicity (one required parameter, output schema exists), the description is nearly complete but lacks minimal behavioral details like what happens if id does not exist.

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

Parameters1/5

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

Schema description coverage is 0% and the description adds no meaning to the time_away_id parameter. No format, example, or constraints beyond it being a required string.

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?

Description clearly states the verb (retrieve), resource (time-away record), and method (by id). It distinguishes itself from sibling tool list_time_away which retrieves multiple records.

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 versus alternatives (e.g., list_time_away). No mention of prerequisites or constraints.

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