Skip to main content
Glama
remuzel

Polarsteps MCP Server

by remuzel

get_trip

Retrieve detailed trip information from Polarsteps including timeline, route, locations, weather, and engagement metrics for comprehensive travel data analysis.

Instructions

Get comprehensive details about a specific trip including summary, timeline, route information, individual steps/locations, weather data, and engagement metrics. Use after get_trip_log when you need detailed information about specific locations or comprehensive trip data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trip_idYesThe unique numerical identifier of a Polarsteps trip (typically 7+ digits)
n_stepsNoMaximum number of trip steps/locations to include in the response (each step contains photos and descriptions from specific locations).

Implementation Reference

  • Main handler function for the 'get_trip' tool. Validates input, fetches trip data using _get_trip utility, handles errors, and returns formatted TextContent response.
    def get_trip(
        polarsteps_client: PolarstepsClient, input: GetTripInput
    ) -> list[TextContent]:
        trip = _get_trip(polarsteps_client, input.trip_id)
        if trip.id == -1:
            return single_text_content(f"Could not find trip with ID: {input.trip_id}")
        return single_text_content(trip.to_detailed_summary(input.n_steps))
  • Pydantic input schema/model for the 'get_trip' tool, defining required trip_id and optional n_steps parameters with descriptions and validation.
    class GetTripInput(BaseModel):
        trip_id: int = Field(
            ...,
            description="The unique numerical identifier of a Polarsteps trip (typically 7+ digits)",
            ge=1_000_000,
        )
        n_steps: int = Field(
            5,
            ge=0,
            description="Maximum number of trip steps/locations to include in the response (each step contains photos and descriptions from specific locations).",
        )
  • PolarstepsTool.TRIP enum entry registering the 'get_trip' tool with its name, description, and input schema reference. Used by server.list_tools().
    TRIP = (
        "get_trip",
        "Get comprehensive details about a specific trip including summary, timeline, route information, individual steps/locations, weather data, and engagement metrics. Use after get_trip_log when you need detailed information about specific locations or comprehensive trip data.",
        GetTripInput,
    )
  • Low-level utility function that calls the Polarsteps API to retrieve trip data and handles error cases by returning a dummy Trip object.
    def _get_trip(polarsteps_client: PolarstepsClient, trip_id: int) -> Trip:
        api_response = polarsteps_client.get_trip(str(trip_id))
        if api_response.is_error or api_response.trip is None:
            return Trip(id=-1, uuid="00000000-0000-4000-8000-000000000000")
        return api_response.trip
  • Dispatch handler in MCP server's call_tool method that matches on tool name, parses args into input model, and invokes the get_trip function.
    case PolarstepsTool.TRIP:
        input = GetTripInput(**args)
        return get_trip(client, input)
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what data is returned (comprehensive details including specific elements) and provides usage sequencing guidance, but doesn't mention important behavioral aspects like error conditions, rate limits, authentication requirements, or pagination behavior for the n_steps parameter.

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 appropriately sized with two sentences that each serve distinct purposes: the first describes what the tool returns, the second provides usage guidance. It's front-loaded with the core functionality. Could be slightly more concise by combining elements, but overall efficient with zero wasted words.

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?

For a tool with no annotations and no output schema, the description provides good purpose and usage guidance but lacks important contextual information. It doesn't describe the return format, error handling, or behavioral constraints. The description compensates somewhat with detailed content listing, but doesn't fully address the gaps left by missing structured metadata.

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?

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema descriptions. It mentions 'individual steps/locations' which relates to the n_steps parameter but doesn't provide additional semantic context beyond the schema's description.

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 tool's purpose with specific verbs ('Get comprehensive details') and resources ('about a specific trip'), listing the exact data elements returned (summary, timeline, route information, steps/locations, weather data, engagement metrics). It effectively distinguishes this from sibling tools like get_trip_log by specifying 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool versus alternatives: 'Use after get_trip_log when you need detailed information about specific locations or comprehensive trip data.' This clearly differentiates it from get_trip_log and implies it's for more detailed information than basic trip listing tools like get_trips.

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