Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

get_job_role

Retrieve a job role's details by its ID from Humaans HRIS.

Instructions

Retrieve a single job role by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_role_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_job_role' tool. It accepts a job_role_id string, makes a GET request to the Humaans API endpoint /job-roles/{job_role_id}, and returns the response as a dictionary.
    @mcp.tool()
    async def get_job_role(job_role_id: str) -> dict[str, Any]:
        """Retrieve a single job role by id."""
        return await client().get(f"/job-roles/{job_role_id}")
  • The tool is registered via the @mcp.tool() decorator from FastMCP, which registers 'get_job_role' as an MCP tool.
    @mcp.tool()
    async def get_job_role(job_role_id: str) -> dict[str, Any]:
        """Retrieve a single job role by id."""
        return await client().get(f"/job-roles/{job_role_id}")
  • The get() helper method on HumaansClient used by the handler to make the actual HTTP GET request to the Humaans API.
    async def get(self, path: str, params: dict[str, Any] | None = None) -> Any:
        clean = {k: v for k, v in (params or {}).items() if v is not None}
        resp = await self._client.get(path, params=clean)
        if resp.status_code >= 400:
            try:
                body = resp.json()
            except Exception:
                body = resp.text
            raise HumaansError(resp.status_code, path, body)
        return resp.json()
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'retrieve', indicating a read operation, but discloses no other behavioral traits such as authentication requirements, rate limits, or that it returns a full job role object.

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 sentence with no wasted words. It is appropriately sized for the simple retrieval task.

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 low complexity and presence of an output schema (likely documenting return values), the description is adequate but minimal. It does not mention error conditions or what the output contains, but the output schema presumably covers that. A more complete description could add value.

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

Parameters1/5

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

Schema description coverage is 0% and the description adds no meaning beyond the schema. It does not explain what 'job_role_id' is, its format, or constraints. With 0% coverage, the description should compensate but fails to do so.

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 'Retrieve a single job role by id.' clearly specifies the action (retrieve), the resource (a single job role), and the means (by id). It distinguishes itself from sibling 'list_job_roles' which retrieves multiple.

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

Usage Guidelines3/5

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

The description implies usage when a specific ID is known, but lacks explicit guidance on when to use this tool versus alternatives like 'list_job_roles'. No exclusions or when-not-to-use provided.

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