Skip to main content
Glama
stefanstranger

mcp-server-vanmoof

get_world_rides_thisweek

Retrieve weekly global ride statistics from VanMoof riders, including average distance, total rides, and average duration metrics.

Instructions

    Retrieves total world rides summary from VanMoof riders.


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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_world_rides_thisweek' MCP tool. It authenticates with the VanMoof API, retrieves rider and bike data, queries the weekly rides endpoint for the current week, extracts the 'world' summary from the carousel, converts average duration to minutes, and returns the result.
    @mcp.tool()
    def get_world_rides_thisweek()-> Dict[str, Any]:
        """
        Retrieves total world rides summary from VanMoof riders.
    
    
        Returns:
            The a summary of the total rides of the VanMoof rider city if authentication is successful, otherwise None.
            The following information is returned:
            - Average distance in km
            - Total Rides
            - Average duration in minutes
        """
        # 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)    
    
        result = response.json().get('carousel', {}).get('world', {})
        # Convert the average duration from milliseconds to minutes.
        result['averageDuration'] = round(result['averageDuration'] / 1000 / 60, 2)
            
        return result
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 that authentication is required for successful retrieval and specifies the return format (summary with average distance, total rides, average duration), which adds useful context. However, it doesn't cover other behavioral aspects like rate limits, error handling, or data freshness, leaving gaps in transparency.

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 and front-loaded, starting with the core purpose. The 'Returns' section is structured but includes a minor grammatical error ('The a summary'), which slightly affects clarity. Overall, it's efficient with minimal waste, though it could be more polished.

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 the tool has no parameters, no annotations, and no output schema, the description provides basic information on purpose, authentication requirement, and return format. However, it lacks details on error cases (e.g., what 'otherwise None' entails), data scope limitations, or how it differs from sibling tools, making it adequate but with clear gaps for a retrieval tool.

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 the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here. Since there are no parameters, the baseline score is 4, as the description doesn't need to compensate for any gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Retrieves total world rides summary from VanMoof riders,' which provides a clear verb ('retrieves') and resource ('world rides summary'), but it doesn't distinguish this from sibling tools like 'get_rides_summary' or 'get_rides_for_week,' making the purpose somewhat vague in context. It specifies 'world' scope, which helps differentiate from city-level tools, but lacks explicit comparison to similar global tools.

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 like 'get_rides_summary' or 'get_rides_for_week,' nor does it mention prerequisites or exclusions. It implies usage for authentication-based retrieval but doesn't clarify context or alternatives, leaving the agent with minimal 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/stefanstranger/mcp-server-vanmoof'

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