Skip to main content
Glama
claracarspt

Clara Carros MCP server

Official
by claracarspt

search_inventory

Search Clara Carros' used car inventory in Portugal. Filter by make, model, fuel type, maximum price, and minimum year to find matching cars with price, year, mileage, and a link.

Instructions

Search Clara Carros' current stock of used cars in Portugal. Filter by make, model, fuel, max price and min year. Returns matching cars with price, year, mileage and a link. IMPORTANT — pass make/model canonically in Latin, as the Portuguese market lists them: make = full brand name ('BMW', 'Mercedes-Benz' not 'Mercedes', 'Volkswagen' not 'VW'); model = the short series/model WITHOUT the engine or trim suffix — BMW: series number only ('320','330','116', not '330e'/'320d'/'3 Series'); Mercedes: class + number ('C 220','E 220','A 250', not 'C220d'/'C-Class'); other brands: plain model name ('Golf','Corolla','3008', not 'Golf 1.5 TSI'). Put the engine/fuel in the fuel field, not the model. If unsure of the exact spelling, call list_makes_models first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fuelNoFuel: petrol, diesel, hybrid, phev, electric, lpg
makeNoFull brand name in Latin, as the market lists it — 'BMW', 'Mercedes-Benz' (not 'Mercedes'), 'Volkswagen' (not 'VW'), 'Peugeot', 'Seat'.
limitNoMax results (default 20)
modelNoShort model/series WITHOUT engine or trim. BMW: series number only ('320','330','116', not '330e'/'320d'/'3 Series'). Mercedes: class + number ('C 220','E 220','A 250', not 'C220d'/'C-Class'). Others: plain model name ('Golf','Corolla','3008', not 'Golf 1.5 TSI').
min_yearNoEarliest registration year
max_priceNoMaximum price in EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so the description must disclose behavior. It states it returns matching cars with price, year, mileage, and a link. No mention of error handling or side effects, but the read-only nature is implied.

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 front-loaded with the core function and filters, then provides detailed formatting rules. Every sentence adds value, though the canonical instructions are lengthy but necessary.

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

Completeness4/5

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

Has no output schema, but the description lists return fields. It references a sibling tool for disambiguation. For a search tool, the description is complete enough to guide the agent.

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

Parameters5/5

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

Input schema covers all 6 parameters with descriptions (100% coverage), but the description adds critical canonical naming conventions for make and model, and clarifies that fuel should be in the fuel field, not model. This goes beyond the schema.

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

Purpose5/5

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

The description clearly states the tool searches Clara Carros' current used car stock in Portugal with specific filters. It distinguishes itself from sibling tools like list_makes_models and get_car by focusing on inventory browsing.

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

Usage Guidelines4/5

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

Provides explicit guidelines for canonical make/model formatting and instructs to call list_makes_models if unsure. While it doesn't explicitly state when not to use the tool, the context is clear.

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