Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

list_equipment

Retrieve equipment assigned to employees. Optionally filter by person ID to see equipment for a specific individual.

Instructions

List equipment assigned to people. Optionally filter by personId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idNo

Implementation Reference

  • The tool handler function that lists equipment from the Humaans API, optionally filtered by personId. It calls list_page on the /equipment endpoint.
    @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 @mcp.tool() decorator registers list_equipment as an MCP tool.
    @mcp.tool()
  • The list_page helper method on HumaansClient that performs the actual API call with pagination params.
    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 client() helper that provides a singleton HumaansClient instance used by list_equipment.
    def client() -> HumaansClient:
        global _client
        if _client is None:
            _client = HumaansClient()
        return _client
Behavior2/5

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

Without annotations, the description carries full burden. It only states the action and filter, not behavioral traits like read-only, pagination, authorization needs, or side effects. This is minimal disclosure for a list operation.

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?

Two efficient sentences, front-loaded with the main action and filter. No redundant information.

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?

For a simple tool with one optional parameter and no output schema, the description is adequate but lacks return value format or details on what 'list equipment' entails (e.g., fields returned). Could be more complete.

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?

Schema description coverage is 0%, so description must compensate. It adds meaning by explaining the parameter is for filtering by person and is optional. Though format not specified, the context is sufficient for a simple 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?

The description clearly states the action ('List equipment') and the resource ('assigned to people'). Among many 'list_*' sibling tools, this is the only one for equipment, providing distinct purpose.

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

Usage Guidelines4/5

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

The description mentions optional filtering by 'personId,' giving clear usage context. However, it lacks explicit guidance on when not to use this tool or alternatives, though no alternatives exist for equipment listing.

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