No user-submitted related servers found.
Scored across 12 tools
Several tools overlap in scope: get_telematic_data and get_vehicle_status both return mileage and CBS data, and get_vehicle_basic_data vs report_product_update_step both touch puStep. The descriptions help somewhat, but agents could easily select the wrong tool when looking for basic maintenance information.
Tool names largely follow a snake_case verb_noun pattern (get_*, list_*, search_*, report_*, diagnose_*). The consistent use of get_ for most data-access operations is clear, though the mix of verbs like report and diagnose with more generic get_/list_ prevents a perfect 5.
12 tools is well within the ideal range for a vehicle-data-focused server. Each tool maps to a distinct BMW CarData concern (catalog search, quota, vehicle mappings, basic data, telematics, tyres, fuel, faults, etc.), and the count feels neither sparse nor bloated.
The toolset covers major vehicle data areas well, but there is no way to fetch arbitrary descriptor values even though search_descriptors exposes a local catalog of 294 descriptors. This creates a notable dead end: agents can discover descriptors but cannot retrieve their actual values through the MCP surface.