Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

list_job_roles

Retrieve historical and current job assignments with optional filtering by person ID to view specific employee's job roles.

Instructions

List job roles (historical and current job assignments). Optionally filter by personId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idNo
limitNo
skipNo

Implementation Reference

  • The handler function that executes the list_job_roles tool. It calls client().list_page() on the '/job-roles' endpoint, with optional filtering by personId, limit, and skip parameters.
    @mcp.tool()
    async def list_job_roles(person_id: str | None = None, limit: int = 100, skip: int = 0) -> Any:
        """List job roles (historical and current job assignments). Optionally filter by personId."""
        return await client().list_page(
            "/job-roles", filters={"personId": person_id}, limit=limit, skip=skip
        )
  • The tool is registered via the @mcp.tool() decorator on line 261, which registers list_job_roles as a tool in the FastMCP server.
    @mcp.tool()
  • The list_page helper method on HumaansClient that performs the actual HTTP GET request with pagination parameters ($limit, $skip) and filter query 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)
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It doesn't mention that the operation is read-only, what fields are returned, or any limitations. The inclusion of historical and current roles is good, but more behavioral context (e.g., default ordering, pagination behavior) is missing.

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 short sentence that is front-loaded and free of fluff. It quickly conveys the main purpose and a key optional parameter. While very concise, it could be slightly more informative without being overly verbose.

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

Completeness1/5

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

Given no annotations, no output schema, and 3 parameters with zero schema descriptions, the description is severely lacking. It does not explain pagination, return format, or how the data is structured. The agent is left with many unknowns, especially with many sibling list tools.

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?

Schema description coverage is 0%, so the description should compensate. It only mentions personId (redundant with parameter name) and does not explain limit (page size) or skip (offset). An agent needs to know that limit and skip control pagination.

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 job roles, including both historical and current assignments. It also mentions an optional filter by personId. This distinguishes it from sibling tools like get_job_role (which retrieves a single role) and other list tools, though it could be slightly more precise about the output being a list.

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 vs alternatives like get_job_role. For example, it doesn't suggest that list_job_roles is for multiple roles or filtering, while get_job_role is for a specific role. Also, pagination parameters (limit, skip) are not explained in the description.

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