Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

list_bank_accounts

Fetch bank accounts for employees. Optionally filter by person ID to get specific account details.

Instructions

List bank accounts. Optionally filter by personId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idNo

Implementation Reference

  • The tool handler function decorated with @mcp.tool(). Calls the HumaansClient.list_page() method with the '/bank-accounts' endpoint and an optional personId filter.
    @mcp.tool()
    async def list_bank_accounts(person_id: str | None = None) -> Any:
        """List bank accounts. Optionally filter by personId."""
        return await client().list_page("/bank-accounts", filters={"personId": person_id}, limit=250)
  • The tool is registered with MCP via the @mcp.tool() decorator on the list_bank_accounts function.
    @mcp.tool()
    async def list_bank_accounts(person_id: str | None = None) -> Any:
  • The list_page method of HumaansClient that performs the actual API call. It builds query parameters (including filters and pagination) and calls the GET endpoint.
    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() helper function that lazily initializes and returns the HumaansClient singleton used by the tool handler.
    def client() -> HumaansClient:
        global _client
        if _client is None:
            _client = HumaansClient()
        return _client
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, return format, pagination, or authorization requirements. The description carries the full burden for transparency but fails to address it.

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 front-loaded sentence with no wasted words. It efficiently conveys the core functionality and optional filter.

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 no output schema and no annotations, the description provides the essential function and filter, but lacks details on return structure or behavior (e.g., pagination, sorting). It is minimally acceptable for a list tool.

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

Parameters3/5

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

The description mentions the optional 'personId' filter, adding context beyond the schema's title 'Person Id'. However, it does not explain the format or meaning of personId. Since schema description coverage is 0%, the description partially compensates.

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 clearly states the action ('List') and resource ('bank accounts'), and distinguishes from sibling tools like list_companies or list_people. The addition of optional filtering adds specificity.

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 mentions optional filtering by personId, which gives some context on when to use filtering, but does not provide guidance on when not to use this tool or suggest alternatives. Since no sibling tool performs a similar function, the lack of exclusions is acceptable.

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