Skip to main content
Glama
JavidGlyv

Turbo.az MCP Server

by JavidGlyv

get_trending

Fetch trending vehicle listings from Turbo.az to discover popular or newly posted cars, trucks, and other automotive options.

Instructions

Fetches most popular/new listings on Turbo.az.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoCategory: new, popular, vipnew
limitNoResult count (default: 20)

Implementation Reference

  • The actual implementation of the get_trending tool logic.
    async def get_trending(self, category: str = "new", limit: int = 20) -> dict:
        """Gets newest/popular listings."""
        
        if category == "vip":
            url = f"{BASE_URL}/autos?q[extras][]=vip"
        elif category == "popular":
            url = f"{BASE_URL}/autos?order=view_count"
        else:  # new
            url = f"{BASE_URL}/autos"
    
        # Use search_cars function
        return await self.search_cars(limit=limit)
  • src/server.py:160-178 (registration)
    Registration of the get_trending tool in the server.
    Tool(
        name="get_trending",
        description="Fetches most popular/new listings on Turbo.az.",
        inputSchema={
            "type": "object",
            "properties": {
                "category": {
                    "type": "string",
                    "description": "Category: new, popular, vip",
                    "default": "new"
                },
                "limit": {
                    "type": "integer",
                    "description": "Result count (default: 20)",
                    "default": 20
                }
            }
        }
    )
  • The tool call handler for get_trending in the server.
    elif name == "get_trending":
        category = arguments.get("category", "new")
        limit = arguments.get("limit", 20)
        results = await scraper.get_trending(category, limit)
        return [TextContent(type="text", text=json.dumps(results, ensure_ascii=False, indent=2))]
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'fetches' implying a read operation, but doesn't cover aspects like rate limits, authentication needs, pagination, or what the return format looks like. This is inadequate for a tool with no annotation support.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero waste—it directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 the tool returns (e.g., listing details, format), potential errors, or behavioral traits like performance or limitations. For a tool fetching data, this leaves significant gaps in understanding its full context.

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?

Schema description coverage is 100%, so the schema already documents both parameters ('category' and 'limit') with descriptions and defaults. The description adds no additional meaning beyond what the schema provides, such as explaining the significance of 'popular' vs 'new' or usage constraints, meeting the baseline for high coverage.

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') and resource ('most popular/new listings on Turbo.az'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'search_cars' or 'get_car_details', which prevents a perfect score.

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 no guidance on when to use this tool versus alternatives like 'search_cars' or 'get_car_details'. It mentions 'most popular/new listings' but doesn't clarify scenarios where this is preferred over a general search or detailed lookup, leaving usage context ambiguous.

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