Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

list_people

Retrieve a list of employees from Humaans. Filter by email, location, or status, and paginate results using limit and skip.

Instructions

List people (employees). Optional filters: email, locationId, status. Paginated via limit/skip (max 250). Note: Humaans has no manager-side filter on this endpoint — use get_direct_reports for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
location_idNo
statusNo
limitNo
skipNo

Implementation Reference

  • The list_people handler function itself, decorated with @mcp.tool(). Queries the Humaans /people endpoint with optional filters (email, locationId, status) and pagination (limit/skip, max 250). Calls client().list_page('/people', ...).
    @mcp.tool()
    async def list_people(
        email: str | None = None,
        location_id: str | None = None,
        status: str | None = None,
        limit: int = 100,
        skip: int = 0,
    ) -> Any:
        """List people (employees). Optional filters: email, locationId, status. Paginated via limit/skip (max 250). Note: Humaans has no manager-side filter on this endpoint — use get_direct_reports for that."""
        filters = {
            "email": email,
            "locationId": location_id,
            "status": status,
        }
        return await client().list_page("/people", filters=filters, limit=limit, skip=skip)
  • FastMCP instance ('mcp') that registers the tool via the @mcp.tool() decorator on line 42.
    mcp = FastMCP("humaans")
  • The HumaansClient.list_page helper method called by list_people to perform the actual HTTP GET request with limit/skip pagination to the Humaans API.
    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)
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses pagination behavior (limit/skip, max 250) but does not mention whether the operation is read-only, any authentication requirements, default ordering, or what happens if no results are found. The pagination limit is useful but more detail would improve transparency.

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?

The description is concise with two sentences, no wasted words. It front-loads the core purpose and then provides essential details about filters and pagination. Every sentence adds value.

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 no output schema, the description should hint at what the tool returns. It does not mention the return structure (e.g., a list of people objects) or any response fields. For a 5-parameter tool with no annotations, this omission leaves the agent without complete context on the tool's output.

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?

Given 0% schema description coverage, the description adds meaning by listing the optional filters (email, locationId, status) and pagination parameters (limit/skip). However, it does not describe valid values or formats (e.g., what status values are accepted) and uses 'locationId' instead of the schema's 'location_id', causing slight inconsistency. It adds moderate value but could be more precise.

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 tool lists people (employees), mentions optional filters, and differentiates from the sibling get_direct_reports by noting the absence of a manager-side filter. The verb 'List' and resource 'people' are specific and unambiguous.

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

Usage Guidelines5/5

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

The description provides guidance by noting the optional filters and pagination, and explicitly advises using get_direct_reports for manager-side filtering. This helps the agent decide when to use this tool versus a sibling.

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