Skip to main content
Glama
stefanstranger

mcp-server-vanmoof

get_rides_summary

Retrieve ride statistics including total rides, distance, and average duration for authenticated VanMoof riders to analyze cycling activity.

Instructions

    Retrieves total rides summary for the VanMoof rider being authenticated.


    Returns:
        The a summary of the total rides of the VanMoof rider if authentication is successful, otherwise None.
        The following information is returned:
        - Average distance in km
        - Total Rides
        - Average duration in minutes
        - Total distance in km
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the get_rides_summary MCP tool. It authenticates with the VanMoof API, retrieves rider and bike IDs, constructs a request for weekly rides summary, and returns the summary data including average distance, total rides, average duration, and total distance.
    @mcp.tool()
    def get_rides_summary()-> Dict[str, Any]:
        """
        Retrieves total rides summary for the VanMoof rider being authenticated.
    
    
        Returns:
            The a summary of the total rides of the VanMoof rider if authentication is successful, otherwise None.
            The following information is returned:
            - Average distance in km
            - Total Rides
            - Average duration in minutes
            - Total distance in km
        """
        # Get the Bearer token from the authenticate method
        token = VanMoofAPI.get_vanmoof_token(VANMOOF_USERNAME, VANMOOF_PASSWORD)
        application_token = VanMoofAPI.get_application_token(token)
        if not application_token:
            return {"error": "Authentication failed"}
    
        # Get the riderId from the customer data
        customerData = VanMoofAPI.get_customer_data()
        riderId = customerData.get('data', {}).get('uuid')
        if not riderId:
            return {"error": "RiderId not found"}
        bikeId = customerData.get('data', {}).get('bikes', [{}])[0].get('id')
        if not bikeId:
            return {"error": "BikeId not found"}
        country = customerData.get('data', {}).get('country')
        if not country:
            return {"error": "CountryCode not found"}
    
        last_seen_week = datetime.now().strftime("%Y-%m-%d")
    
        # Ensure last_seen_week is the Monday of the week
        date_obj = datetime.strptime(last_seen_week, "%Y-%m-%d")
        monday = date_obj - timedelta(days=date_obj.weekday())
        last_seen_week = monday.strftime("%Y-%m-%d")
    
        url = f"https://tenjin.vanmoof.com/api/v1/rides/{riderId}/{bikeId}/weekly"
        querystring = {"lastSeenWeek": last_seen_week, "limit": str(1)}
    
        headers = {
            "authorization": f"Bearer {application_token}",
            "api-key": "fcb38d47-f14b-30cf-843b-26283f6a5819",
            "cache-control": "no-cache, private",
            "accept-language": f"{country.lower()}_{country.upper()}",
            "accept-encoding": "gzip",
            "timezone": timezone_name,
            "accept": "*/*",
        }
        response = requests.get(url, headers=headers, params=querystring)
        return response.json().get('carousel', {}).get('summary', {})
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 mentions authentication dependency ('if authentication is successful, otherwise None'), which is useful context. However, it lacks details on rate limits, error handling, or data freshness, leaving gaps in behavioral understanding for a tool that likely involves user-specific data retrieval.

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 well-structured and concise, with a clear purpose statement followed by return details. It uses two paragraphs efficiently, though the 'Returns:' section could be slightly more streamlined. Overall, it avoids fluff and stays focused on essential information.

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 annotations and no output schema, the description provides basic purpose and output details but lacks comprehensive context. It explains the return format (summary with specific metrics) and authentication dependency, which is helpful. However, for a tool that likely involves user data, more details on permissions, data sources, or limitations would improve completeness.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose and output. This meets the baseline expectation for tools with no parameters, as it avoids unnecessary repetition.

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 'retrieves total rides summary for the VanMoof rider being authenticated,' specifying the verb (retrieves), resource (rides summary), and scope (for the authenticated rider). It distinguishes from siblings like 'get_rides_for_week' by focusing on summary totals rather than detailed or filtered ride data, though it could be more explicit about this differentiation.

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 implies usage context through 'for the VanMoof rider being authenticated,' suggesting it's for authenticated users, but it does not explicitly state when to use this tool versus alternatives like 'get_rides_for_week' or 'get_city_rides_thisweek.' No guidance on prerequisites, exclusions, or specific scenarios is provided, leaving usage somewhat ambiguous.

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/stefanstranger/mcp-server-vanmoof'

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