Skip to main content
Glama
ptorsten

humaans-mcp

by ptorsten

list_locations

Retrieve all configured work locations, such as countries or regions, for your remote teams.

Instructions

List all configured work locations (typically countries/regions for remote teams).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `list_locations` tool handler: calls the Humaans API client to list all configured work locations (countries/regions) with a limit of 250.
    @mcp.tool()
    async def list_locations() -> Any:
        """List all configured work locations (typically countries/regions for remote teams)."""
        return await client().list_page("/locations", limit=250)
  • The `list_page` helper method on HumaansClient that list_locations delegates to. It calls the API with pagination parameters ($limit, $skip).
    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 `@mcp.tool()` decorator registers `list_locations` as an MCP tool on the FastMCP 'humaans' server.
    @mcp.tool()
    async def list_locations() -> Any:
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 disclosing behavior. It states a read operation ('List all') but omits details on authentication, rate limits, empty results, or whether the list is paginated. This gap lowers transparency.

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, well-structured sentence with no redundant words. Every phrase adds value: 'List all' indicates scope, 'configured work locations' defines the entity, and the parenthetical clarifies typical usage.

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?

Given zero parameters and no output schema, the description sufficiently covers the purpose and expected output. It could mention that results are a list of location strings or objects, but the lack of complexity makes it adequate.

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 no parameters (100% coverage by definition). The description adds meaning by specifying the resource ('work locations') and typical content ('countries/regions for remote teams'), which aids the agent beyond the empty schema.

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 explicitly states the tool lists all configured work locations and provides clarifying context (typically countries/regions for remote teams). This verb-resource combination is distinct from sibling tools like list_people or list_documents, ensuring unambiguous purpose.

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?

While the description implies the tool is for retrieving location data for remote teams, it offers no explicit guidance on when to use it versus alternatives. No sibling tool directly conflicts, but a statement about prerequisites or exclusivity would strengthen this dimension.

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