Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

list_compensations

Retrieve compensation records including salary and bonus. Filter by person ID or compensation type ID.

Instructions

List compensation records (salary, bonus, etc.). Optional filters: personId, typeId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idNo
type_idNo
limitNo
skipNo

Implementation Reference

  • The `list_compensations` tool handler. It is decorated with `@mcp.tool()` and accepts optional filters `person_id`, `type_id`, `limit`, and `skip`. It delegates to `HumaansClient.list_page()` on the `/compensations` endpoint.
    @mcp.tool()
    async def list_compensations(
        person_id: str | None = None,
        type_id: str | None = None,
        limit: int = 100,
        skip: int = 0,
    ) -> Any:
        """List compensation records (salary, bonus, etc.). Optional filters: personId, typeId."""
        return await client().list_page(
            "/compensations",
            filters={"personId": person_id, "typeId": type_id},
            limit=limit,
            skip=skip,
        )
  • The `@mcp.tool()` decorator registers `list_compensations` as an MCP tool in the FastMCP server instance.
    @mcp.tool()
    async def list_compensations(
  • The `HumaansClient.list_page()` helper method that `list_compensations` calls. It sends a GET request with `$limit`/`$skip` pagination and optional filters as query parameters.
    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?

With no annotations, the description must disclose behavioral traits. It only states the basic function and optional filters. Important traits like pagination (limit, skip parameters) are not mentioned, nor are aspects like data freshness, idempotency, or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence), which is concise but lacks necessary details. It is front-loaded with the verb 'List', but the overall brevity sacrifices completeness.

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 the absence of annotations, output schema, and schema descriptions, the description should provide more context. It does not explain what fields are returned, pagination behavior, or typical use cases. The tool has 4 parameters but the description only covers 2 superficially.

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

Parameters2/5

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

The description mentions two of four parameters ('personId' and 'typeId' but with different casing from schema), while 'limit' and 'skip' are omitted entirely. Schema coverage is 0%, so the description partially compensates but misses the pagination parameters.

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 verb 'List' and the resource 'compensation records', making the primary purpose obvious. It also mentions optional filters, which adds specificity. However, it does not explicitly differentiate from sibling tools like 'get_compensation', but the context implies this is for 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 is provided on when to use this tool versus alternatives. Siblings include 'get_compensation' for a single record, but the description does not clarify that distinction. There is no mention of prerequisites, use cases, or when not to use.

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