Zipcar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_carsA | Search for available Zipcars near a location for a given time period. Returns a list of available vehicles with rates and locations. |
| get_car_detailsB | Get detailed information about a specific Zipcar including vehicle type, features, seating, fuel type, and pricing rates. |
| reserve_carA | Book a Zipcar for a specific time slot. Requires the user to be logged in to Zipcar. Returns reservation confirmation details. |
| extend_reservationA | Extend an existing Zipcar reservation to a later end time. The car must still be available for the extended period. |
| end_tripA | End an active Zipcar rental session. The car must be parked at a valid Zipcar spot. Returns a trip summary with duration, miles, and cost. |
| get_reservation_historyB | View past and upcoming Zipcar reservations. Can filter by upcoming or past reservations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: end_trip handles active rentals, extend_reservation modifies existing bookings, get_car_details provides vehicle info, get_reservation_history accesses past/future bookings, reserve_car creates new reservations, and search_cars finds available vehicles. The descriptions reinforce these distinct roles, making misselection unlikely.
All tool names follow a consistent verb_noun pattern (e.g., end_trip, extend_reservation, get_car_details), using clear action verbs paired with specific nouns. There are no deviations in style or convention, making the set predictable and easy to understand at a glance.
With 6 tools, this server is well-scoped for managing Zipcar rentals, covering key workflows like searching, reserving, extending, ending trips, and accessing details/history. Each tool earns its place without redundancy, and the count is typical for a focused domain like car-sharing services.
The tool set provides complete coverage for the Zipcar rental lifecycle: search_cars and get_car_details for discovery, reserve_car and extend_reservation for booking management, end_trip for session closure, and get_reservation_history for tracking. There are no obvious gaps, enabling agents to handle end-to-end tasks without dead ends.