Skip to main content
Glama
stefanstranger

mcp-server-vanmoof

by stefanstranger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VANMOOF_PASSWORDYesYour VanMoof user account password
VANMOOF_USERNAMEYesYour VanMoof username (email address)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_customer_dataB
    Retrieves customer data from the vanMoof API.

    Returns:
        The rider vanMoof's customer data if authentication is successful, otherwise None.
get_vanmoof_citiesB
    Retrieves a list of city data from the vanMoof API.

    Returns:
        The rider vanMoof's city data if authentication is successful, otherwise None.
get_rider_preferencesB
    Retrieves rider preferences from the vanMoof API.

    Returns:
        The rider preferences if authentication is successful, otherwise None.
get_rides_summaryA
    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_rides_for_weekA
    Retrieves rides for a specific week from the vanMoof API.
    
    Args:
        date_in_week: Any date within the week in format "YYYY-MM-DD".
                    If None, uses the current date.
                    
    Returns:
        The rides for the specified week if authentication is successful, otherwise None.
get_city_rides_thisweekB
    Retrieves total city 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:
        - City name
        - Average distance in km
        - Total Rides
        - Average duration in minutes
        - Location in latitude and longitude
get_world_rides_thisweekB
    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

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.3/5.0

Scored across 7 tools

Disambiguation2/5

Multiple tools have overlapping purposes that could cause confusion. get_city_rides_thisweek, get_rides_summary, and get_world_rides_thisweek all return similar ride summary data with only subtle differences in scope (city vs. world vs. general). get_rides_for_week also overlaps with these but adds a date parameter, creating ambiguity about when to use which summary tool.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming. The naming is perfectly predictable across all seven tools, making it easy to understand the pattern and anticipate tool names.

Tool Count4/5

Seven tools is a reasonable number for a bike sharing/ride tracking API. While the count is appropriate, the tools feel slightly redundant rather than each earning its distinct place due to the overlapping summary tools.

Completeness3/5

The server provides good read operations for customer data, preferences, cities, and rides, but lacks any write/update capabilities. For a rider data API, there are notable gaps - no tools to update preferences, log new rides, or modify customer information, which limits agent workflows to read-only operations.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources