Skip to main content
Glama
yevhen-kalyna

autoria-mcp

get_car_details

Retrieve detailed information for a specific AUTO.RIA car listing by its ID, including price, specifications, seller-declared condition, and risk indicators to verify trustworthiness before making a decision.

Instructions

Get compact details for a single AUTO.RIA advert by its id.

Returns price (USD/UAH/EUR), year, mileage (km), fuel + engine_volume_l

  • power_hp, gearbox, drive, body_name, generation, modification, colour, location, the VIN (only if the seller revealed it), the masked phone, and the canonical listing url.

For due diligence it also returns SELLER-DECLARED, UNVERIFIED provenance: condition (1 undamaged … 4 for-parts), the risk block (damaged/for_parts/under_credit/confiscated/imported/needs_customs), VIN/inspection verification, seller trust, photo links, plus is_sold/is_leasing/price_negotiable/exchange_possible and the seller description. Check risk and condition before trusting a listing — mileage_km and prices are claims, not facts. The phone is always masked. To look up many ids at once use get_car_details_batch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
auto_idYesAdvert id (from `search_used_cars` `ids`).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
vinNo
cityNo
fuelNo
riskNo
yearNo
brandNo
colorNo
driveNo
modelNo
phoneNo
photoNo
titleNo
regionNo
sellerNo
body_idNo
fuel_idNo
gearboxNo
is_soldNo
drive_idNo
power_hpNo
body_nameNo
conditionNo
price_eurNo
price_uahNo
price_usdNo
sold_dateNo
gearbox_idNo
generationNo
is_leasingNo
mileage_kmNo
descriptionNo
listed_dateNo
modificationNo
updated_dateNo
verificationNo
gearbox_classNo
engine_volume_lNo
price_negotiableNo
exchange_possibleNo
engine_volume_classNo
Behavior5/5

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

No annotations provided, but description discloses that phone is always masked, seller-declared data is unverified, and warns about trusting mileage and prices. Provides risk and condition checks.

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?

Description is fairly concise and front-loaded with purpose. Second sentence lists many return fields, which is somewhat verbose but necessary for clarity. Overall well-organized.

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

Completeness5/5

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

Given complexity, schema coverage, and presence of output schema, description is complete. Includes usage guidelines, behavioral warnings, and batch alternative without needing to repeat return values.

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

Parameters4/5

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

Only one parameter auto_id. Schema describes it as advert id from search_used_cars ids. Description adds context that it's for a single advert and reinforces the source of the id. Schema coverage is 100%, so baseline 3, but description adds value.

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 gets compact details for a single AUTO.RIA advert by its id. It distinguishes from sibling get_car_details_batch, which is for multiple ids.

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?

Explicitly suggests using get_car_details_batch for multiple ids. Warns about trusting seller-declared data. Does not explicitly state when not to use, but context is clear.

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/yevhen-kalyna/autoria-mcp'

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