Skip to main content
Glama
JavidGlyv

Turbo.az MCP Server

by JavidGlyv

get_car_details

Retrieve comprehensive vehicle information from Turbo.az automotive listings using a listing ID or URL to access detailed specifications, pricing, and seller details.

Instructions

Fetches detailed listing info from Turbo.az. Requires listing ID or URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listing_idYesListing ID (e.g. 1234567) or full URL

Implementation Reference

  • The main handler function that executes the web scraping logic to fetch car details.
    async def get_car_details(self, listing_id: str) -> dict:
        """Gets detailed information of a specific listing."""
    
        # Can be URL or ID
        if listing_id.startswith("http"):
            url = listing_id
        else:
            url = f"{BASE_URL}/autos/{listing_id}"
        
        logger.info(f"Fetching details: {url}")
        
        def _scrape():
            driver = self._get_driver()
            
            try:
                driver.get(url)
                WebDriverWait(driver, 20).until(
                    EC.presence_of_element_located((By.CLASS_NAME, "product"))
                )
                
                details = {"url": url}
    
                # Title
                try:
                    title = driver.find_element(By.CLASS_NAME, "product-title")
                    details["title"] = title.text.strip()
                except NoSuchElementException:
                    details["title"] = "N/A"
    
                # Price (sidebar: product-price__i--bold)
                try:
                    price = driver.find_element(By.CSS_SELECTOR, ".product-price__i--bold")
                    details["price"] = price.text.strip()
                except NoSuchElementException:
                    try:
                        price = driver.find_element(By.CLASS_NAME, "product-price__i")
                        details["price"] = price.text.strip()
                    except NoSuchElementException:
                        details["price"] = "N/A"
  • src/server.py:133-146 (registration)
    Registration of the 'get_car_details' tool in the MCP server definitions.
    Tool(
        name="get_car_details",
        description="Fetches detailed listing info from Turbo.az. Requires listing ID or URL.",
        inputSchema={
            "type": "object",
            "properties": {
                "listing_id": {
                    "type": "string",
                    "description": "Listing ID (e.g. 1234567) or full URL"
                }
            },
            "required": ["listing_id"]
        }
    ),
  • Logic within the server's call_tool function that routes the 'get_car_details' request to the scraper.
    elif name == "get_car_details":
        listing_id = arguments.get("listing_id")
        if not listing_id:
            return [TextContent(type="text", text="Error: listing_id is required")]
    
        details = await scraper.get_car_details(listing_id)
    
        # Fetch images and include them as ImageContent
        content_list = [TextContent(type="text", text=json.dumps(details, ensure_ascii=False, indent=2))]
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the requirement for a listing ID or URL but doesn't cover other behavioral aspects such as rate limits, authentication needs, error handling, or what 'detailed listing info' includes. This leaves significant gaps for a tool that fetches data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the main action and requirement in a single sentence. There's no wasted text, making it efficient, though it could benefit from slightly more detail to improve completeness without sacrificing brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'detailed listing info' entails, potential response formats, or error cases. For a data-fetching tool with no structured output documentation, this leaves the agent with insufficient context to use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds minimal value beyond the input schema, which has 100% coverage and clearly documents the 'listing_id' parameter. It clarifies that the parameter can be an ID or URL, but this is already implied by the schema's description. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't significantly enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('fetches detailed listing info') and resource ('from Turbo.az'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'search_cars' or 'get_trending' beyond mentioning it's for 'detailed listing info' rather than search or trending data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides minimal guidance by stating it 'requires listing ID or URL', but offers no explicit advice on when to use this tool versus alternatives like 'search_cars' or 'get_trending'. It lacks context on prerequisites or scenarios where this tool is preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JavidGlyv/Turboaz-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server