Skip to main content
Glama
korea-data-mcp

korea-data-mcp

by parkseokjune

encar_listings

Query live Korean used-car listings from Encar with filters for make, model, price, year and mileage, returning English rows with price in KRW, region and a direct link.

Instructions

Return live Korean used-car listings from Encar, Korea's largest used-car marketplace (~200,000 cars). Each row has make_en, model_group_en (e.g. Sonata, Grandeur, 5-Series), year, price_krw, mileage_km, fuel_en, region_en, trim and URL. Generation name and trim stay in Korean as published.

Args: carType: "all", "domestic" or "imported". manufacturer: Make in English or Korean, e.g. "Hyundai", "Kia", "BMW". Empty = all. modelGroup: Model family in English or Korean, e.g. "Grandeur", "Sorento". Empty = all. sort: "newest", "price_asc", "price_desc", "mileage_asc" or "year_desc". salesOnly: True drops lease/rent takeovers (rows with no comparable sale price). includeVinSpec: True adds VIN, transmission, colour and displacement per car (billed extra). maxItems: Maximum number of listings to return (billed per listing).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "encar_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNonewest
carTypeNoall
maxItemsNo
salesOnlyNo
modelGroupNo
manufacturerNo
includeVinSpecNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful conduct: per-listing billing on maxItems, extra billing for includeVinSpec, that salesOnly removes rows lacking a comparable sale price, and that generation name/trim remain untranslated Korean. It omits rate limits, auth requirements, and whether results are cached or paginated beyond maxItems.

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?

Front-loaded with the core purpose and return shape, then a clean Args block mapping one line per parameter. Nearly every sentence earns its place; the returned-field enumeration is slightly verbose given an output schema exists, but it aids selection.

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?

For a 7-parameter, annotation-free tool the description covers source, row shape, all filters, and billing implications, which is enough to invoke correctly. Remaining holes — default values, rate limiting, result pagination — are modest but real.

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?

Schema description coverage is 0%, so the description must compensate, and it does — enumerating all seven parameters with accepted values (carType enums, sort orderings), English/Korean examples, and behavioral meaning for the booleans. The gap is that defaults (maxItems=20, sort=newest) and a maxItems ceiling are not stated.

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?

States a specific verb and resource ("Return live Korean used-car listings from Encar") plus the marketplace's scale and a concrete inventory of returned row fields. This is unambiguously a used-car listing feed, easily separated from siblings like danawa_prices (price comparison) or passo_motorcycles (motorcycles).

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

Usage Guidelines3/5

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

Usage is implied through the filter semantics (Empty = all for manufacturer/modelGroup, salesOnly drops lease/rent takeovers), which tells the agent how to narrow results. However, there is no explicit statement of when to choose this tool over a sibling or when-not to call it, leaving routing to inference.

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