Skip to main content
Glama
slettmayer

wunder-user-mcp

by slettmayer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WUNDER_TENANTYesTenant short-code used in the API URL path.
WUNDER_BASE_URLNoAPI gateway base URL.https://go.api.gourban.services/v1
WUNDER_BRANCH_IDNoDefault branch id for vehicle/rental calls.
WUNDER_HTTP_TIMEOUTNoPer-request timeout in seconds.30
WUNDER_REFRESH_TOKENYesLong-lived refresh token for the end user.
WUNDER_DEFAULT_RADIUS_MINoRadius (miles) used by get_vehicles when a location is given without a radius.5

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_vehiclesA

List available vehicles for the signed-in user.

When both latitude and longitude are supplied, the result is scoped to a radius around that point (radius_miles, defaulting to WUNDER_DEFAULT_RADIUS_MI), each vehicle is annotated with distanceKm/distanceMeters from the user, and the list is sorted by ascending distance. Without a location, vehicles are returned as provided by the API (no distance, no distance sort).

Filters: branch_id, category_ids, exclude_stationed_vehicles (true = free-floating only), min_state_of_charge/max_state_of_charge (battery percentage 0-100).

get_active_rentalA

Retrieve the signed-in user's currently ongoing rental(s).

Returns rentals in ACTIVE (trip in progress) or RESERVATION (held, not yet started) state. Usually 0 or 1. Use a returned rental's id with rental_command to operate it.

rental_commandA

Execute an operation on a rental and return the updated rental.

operation_type (case-sensitive) is one of:

  • START start a reserved rental

  • PARK pause driving while keeping the rental active

  • DRIVE resume driving after a park

  • END end the rental (triggers final checks and billing)

  • OPEN_TAILBOX open a configured tailbox / helmet box / saddle compartment

  • RENEW_RESERVATION extend a reservation where supported Other operation types configured for the tenant are passed through as-is.

Optional fields are forwarded when relevant (mainly for END): file_id (e.g. a parking photo uploaded via POST /files), parking_report, vehicle_code, reason.

Note: ending may be blocked by end-checks (parking/station/photo/surcharge). This tool does not pre-run POST /rentals/{id}/check/end; an END that fails a requirement surfaces the API error.

create_rentalA

Create a rental for the signed-in user, as a reservation or an active rental.

Provide exactly one of vehicle_id (from the map/list) or vehicle_code (from a QR scan). start_rental_state is RESERVATION (hold the vehicle, default) or ACTIVE (start the trip immediately, begins billing).

Optional: additions (selected add-on codes, e.g. ["INSURANCE", "HELMET"]), user_group_code + rental_type="BUSINESS" for business-account billing.

Returns the created rental, including its id and state.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a distinct purpose: creating a rental, retrieving active rentals, listing available vehicles, and executing commands on rentals. There is no overlap or ambiguity between them.

Naming Consistency4/5

Three of the four tools follow a clear verb_noun pattern (create_rental, get_active_rental, get_vehicles), while 'rental_command' deviates slightly as a noun_verb. The inconsistency is minor and the names remain readable.

Tool Count4/5

Four tools is a compact but reasonable set for a user-facing rental service. It covers the essential actions without being too few or too many, though a few more (e.g., cancel reservation) might be expected.

Completeness4/5

The tool surface covers the core workflows: vehicle discovery, rental creation, state monitoring, and lifecycle commands. A minor gap is the lack of an explicit cancel/reservation removal, but the domain is well-served overall.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources