Turbo.az MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROME_BINARY | No | The path to the Google Chrome or Chromium binary. Useful if the browser is installed in a non-standard location or when running inside WSL. |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_carsC | Car search on Turbo.az. Search by make, model, price range, year, etc. |
| get_car_detailsC | Fetches detailed listing info from Turbo.az. Requires listing ID or URL. |
| get_makes_modelsB | Fetches list of available makes and models on Turbo.az. |
| get_trendingC | Fetches most popular/new listings on Turbo.az. |
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 4 tools
Each tool has a clearly distinct purpose with no ambiguity: get_car_details retrieves specific listing details, get_makes_models provides metadata, get_trending shows popular listings, and search_cars enables filtered searches. The descriptions clearly differentiate their functions, making misselection unlikely.
All tools follow a consistent verb_noun pattern with snake_case naming (get_car_details, get_makes_models, get_trending, search_cars). The verbs 'get' and 'search' are appropriately used and maintain a predictable structure throughout the set.
With 4 tools, the server is well-scoped for a car listing domain, covering key operations like searching, viewing details, browsing trends, and accessing metadata. It feels slightly thin but reasonable, as each tool earns its place without redundancy.
The toolset covers core read-only operations for a car listing service: search, detail viewing, trend access, and metadata retrieval. Minor gaps exist, such as no tools for user interactions (e.g., saving favorites or contacting sellers), but agents can perform essential browsing tasks effectively.