Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

get_company

Retrieve a specific company's details by providing its unique identifier.

Instructions

Retrieve a company by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual tool handler for 'get_company'. It accepts a company_id string and makes a GET request to /companies/{company_id} via the HumaansClient.
    @mcp.tool()
    async def get_company(company_id: str) -> dict[str, Any]:
        """Retrieve a company by id."""
        return await client().get(f"/companies/{company_id}")
  • The tool is registered using the @mcp.tool() decorator from FastMCP, which automatically registers it as an MCP tool.
    @mcp.tool()
    async def get_company(company_id: str) -> dict[str, Any]:
        """Retrieve a company by id."""
        return await client().get(f"/companies/{company_id}")
  • The input schema is defined by the function signature: company_id is a required string parameter. The return type is dict[str, Any].
    async def get_company(company_id: str) -> dict[str, Any]:
  • The client().get() helper method that performs the actual HTTP GET request to the Humaans API, which is called by the get_company handler.
    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 indicates a read operation ('retrieve') but fails to disclose error handling, authentication needs, or any side effects. Minimal transparency.

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 concise with a single sentence. While it is not verbose, it could include more details without becoming lengthy.

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 and the presence of an output schema, the description is adequate but lacks information on error conditions or validation. It is minimally complete.

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%, but the description adds no additional meaning beyond the schema. It mentions 'by id' but does not explain the format or purpose of the `company_id` parameter.

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 'Retrieve a company by id,' using a specific verb and resource. However, it does not distinguish from the sibling tool `list_companies`, which could cause confusion about when to use each.

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 like `list_companies`. The description does not provide context for when it is appropriate or inappropriate 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