Skip to main content
Glama
remuzel

Polarsteps MCP Server

by remuzel

get_user_profile

Retrieve a Polarsteps user's profile to view their current location, countries visited, and trip count by providing their username.

Instructions

Get a users' profile overview including their living location and their number of countries visited & trips.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesThe username of the Polarstep user to look for.

Implementation Reference

  • Implements the core logic of the get_user_profile tool by fetching the user via _get_user helper and returning profile text content or error message.
    def get_user_profile(
        polarsteps_client: PolarstepsClient, input: GetUserProfile
    ) -> list[TextContent]:
        user = _get_user(polarsteps_client, input.username)
        if user.id == -1:
            return single_text_content(
                f"User not found: No Polarsteps user exists with username={input.username}. Please verify the username is correct and the user's profile is public."
            )
        return single_text_content(user.to_profile())
  • Pydantic BaseModel defining the input parameters for the get_user_profile tool: username field.
    class GetUserProfile(BaseModel):
        username: str = Field(
            ...,
            description="The username of the Polarstep user to look for.",
        )
  • Registers the 'get_user_profile' tool in the PolarstepsTool enum with name, description, and schema reference.
    USER_PROFILE = (
        "get_user_profile",
        "Get a users' profile overview including their living location and their number of countries visited & trips.",
        GetUserProfile,
    )
  • Dispatches calls to the get_user_profile handler in the server's call_tool method.
    case PolarstepsTool.USER_PROFILE:
        input = GetUserProfile(**args)
        return get_user_profile(client, input)
  • Helper function _get_user that retrieves the user from Polarsteps API by username, returns dummy User if not found.
    def _get_user(polarsteps_client: PolarstepsClient, username: str) -> User:
        api_response = polarsteps_client.get_user_by_username(username)
        if api_response.is_error or api_response.user is None:
            return User(
                id=-1, uuid="00000000-0000-4000-8000-000000000000", username="unknown"
            )
        return api_response.user
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves profile data, implying a read-only operation, but doesn't address key behavioral aspects such as authentication requirements, error handling (e.g., for invalid usernames), rate limits, or response format. The description adds minimal context beyond the basic purpose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose. It avoids redundancy and wastes no words, though it could be slightly more structured (e.g., by separating usage context). Every part of the sentence contributes meaning, making it appropriately concise.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete for a tool with one parameter. It specifies what data is retrieved but omits critical context such as authentication needs, error scenarios, or the structure of the returned profile overview. For a read operation with no structured output documentation, more behavioral and response details are needed.

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 schema description coverage is 100%, with the single parameter 'username' clearly documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides (e.g., format constraints or examples). Since the schema handles the parameter documentation adequately, the baseline score of 3 is appropriate.

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 the tool's purpose: 'Get a users' profile overview' with specific content details ('living location and their number of countries visited & trips'). It uses a specific verb ('Get') and identifies the resource ('profile overview'), but doesn't explicitly distinguish it from sibling tools like 'get_user_social' or 'get_user_stats' which might provide overlapping or related user information.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_user_social' or 'get_user_stats', nor does it specify prerequisites, exclusions, or contextual cues for selection. Usage is implied by the purpose but lacks explicit direction.

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/remuzel/polarsteps-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server