Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

list_documents

Retrieve documents from Humaans HRIS. Filter by person ID to find documents for a specific employee.

Instructions

List documents. Optionally filter by personId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idNo

Implementation Reference

  • The list_documents MCP tool handler function. It optionally filters by personId and calls client().list_page('/documents', ...) to fetch documents from the Humaans API.
    @mcp.tool()
    async def list_documents(person_id: str | None = None) -> Any:
        """List documents. Optionally filter by personId."""
        return await client().list_page("/documents", filters={"personId": person_id}, limit=250)
  • The @mcp.tool() decorator registers list_documents (and other tools) with the FastMCP server. The tool is defined as an async function and registered automatically via the decorator.
    @mcp.tool()
    async def list_equipment(person_id: str | None = None) -> Any:
        """List equipment assigned to people. Optionally filter by personId."""
        return await client().list_page("/equipment", filters={"personId": person_id}, limit=250)
  • The list_page helper method on HumaansClient that list_documents calls. It constructs query parameters ($limit, $skip, filters) and performs an HTTP GET request to the given API path.
    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)
  • The get helper method that executes the actual HTTP GET request and handles error responses. Called by list_page.
    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 are provided, and the description does not disclose any behavioral traits such as read-only, permissions, pagination, or effects. The burden is on the description, which is minimal.

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, direct sentence that conveys the core purpose without unnecessary words. It is front-loaded with the primary action.

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

Completeness4/5

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

For a simple list tool with one optional parameter, the description provides sufficient information to understand its function. An output schema is absent, but the return values are implied.

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 states the parameter is optional and used for filtering, but the name in description ('personId') does not match the schema ('person_id'). No details on format or constraints beyond the schema's type definition.

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) and resource (documents), and mentions an optional filter by personId, which distinguishes it from sibling list_* tools.

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 vs alternatives; no mention of preconditions or scenarios where it is preferred.

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