Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

list_custom_values

List custom field values for employees. Optionally filter results by person ID to get specific entries.

Instructions

List custom field values. Optionally filter by personId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idNo

Implementation Reference

  • The MCP tool handler for 'list_custom_values'. It calls the Humaans API /custom-values endpoint with an optional personId filter, paginating with a limit of 250.
    @mcp.tool()
    async def list_custom_values(person_id: str | None = None) -> Any:
        """List custom field values. Optionally filter by personId."""
        return await client().list_page("/custom-values", filters={"personId": person_id}, limit=250)
  • The tool is registered with FastMCP via the @mcp.tool() decorator on line 418, making it available as an MCP tool named 'list_custom_values'.
    @mcp.tool()
    async def list_custom_values(person_id: str | None = None) -> Any:
        """List custom field values. Optionally filter by personId."""
        return await client().list_page("/custom-values", filters={"personId": person_id}, limit=250)
  • Helper method list_page on HumaansClient that constructs pagination parameters and delegates to the GET helper. Called by list_custom_values to make the API request.
    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)
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 behavioral traits such as read-only nature, authorization requirements, or result limits. For a list operation, these are important.

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 a single concise sentence that directly conveys the tool's purpose and parameter use, with no extraneous 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?

Given the tool's simplicity (1 optional param, no output schema), the description covers the basics but omits details like output format, pagination, or default behavior.

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?

The single parameter person_id has no schema description (0% coverage), but the tool description explains its role as an optional filter, adding valuable meaning beyond the schema's title.

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 it lists custom field values with optional filtering by personId. It is specific about verb and resource, but does not differentiate from sibling 'list_custom_fields'.

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. There are many sibling tools, and the description offers no context for selection.

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