Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

list_companies

Retrieve all companies in your Humaans account.

Instructions

List all companies in the Humaans account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for 'list_companies' — an async function decorated with @mcp.tool() that calls the Humaans API to list all companies (limit=250).
    @mcp.tool()
    async def list_companies() -> Any:
        """List all companies in the Humaans account."""
        return await client().list_page("/companies", limit=250)
  • The tool is registered via the @mcp.tool() decorator on the FastMCP instance 'mcp'.
    @mcp.tool()
    async def list_companies() -> Any:
  • The HumaansClient.list_page() helper method that builds the HTTP GET request with pagination params ($limit, $skip) and calls the API.
    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)
  • The client() singleton factory that provides the HumaansClient instance used by list_companies.
    def client() -> HumaansClient:
        global _client
        if _client is None:
            _client = HumaansClient()
        return _client
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states it lists all companies, with no mention of performance, pagination, permissions, or data freshness. For a simple read operation, this is minimal disclosure.

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 that fully conveys the tool's purpose. No unnecessary words or repetition.

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

Completeness4/5

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

For a zero-parameter list tool with no output schema, the description sufficiently explains what the tool does. It could optionally mention typical returned fields or ordering, but the core function is clear. Given the low complexity, it is mostly complete.

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 input schema has zero parameters with 100% coverage. The description adds no parameter info, but this is acceptable since there are none. Baseline 4 is appropriate.

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 'List all companies in the Humaans account.' uses a specific verb ('list') and resource ('companies') with clear scope ('all in the account'). It distinguishes itself from the sibling tool 'get_company' which retrieves a single company, and from other list tools targeting different resources.

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 clearly states the tool's function but provides no guidance on when to use it versus alternatives like 'get_company' (for individual companies). However, the implied usage is straightforward given the no-parameter signature. No exclusions or context are 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