Skip to main content
Glama
korea-data-mcp

korea-data-mcp

by parkseokjune

kbchachacha_listings

Retrieve Korean used-car listings from KB Chachacha with filters for manufacturer, model, sort order, and result limit; returns English fields plus listing URLs for market research and comparison.

Instructions

Return Korean used-car listings from KB Chachacha (KB Financial's marketplace): make_en, model_group_en, year, price_krw, mileage_km, fuel_en, region_en and URL.

Args: manufacturer: Make in English or Korean, e.g. "Kia", "Hyundai". Empty = all. model: Model family in Korean, e.g. "쏘렌토"; requires manufacturer. Empty = all. sort: "newest", "price_asc", "price_desc", "mileage_asc", "mileage_desc" or "year_desc". 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": "kbchachacha_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNonewest
modelNo
maxItemsNo
manufacturerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose non-obvious behavior: results are 'billed per listing', maxItems caps the count, and model filtering requires manufacturer — genuine cost and constraint information not present in the schema. However it omits auth/permission needs, rate or quota limits beyond per-listing billing, pagination, and what happens on invalid Korean model strings.

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 action and the returned fields, followed by a compact Args block — a sensible ordering. The return-field list is slightly long for a tool that has an output schema, but every line otherwise carries information.

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 four-parameter read/filter tool with an output schema and zero annotation coverage, the definition covers filtering semantics, cost implication, and conditional parameter requirements. It is nearly complete; only defaults and failure/auth behavior are absent.

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 largely does: manufacturer accepts English or Korean with empty meaning all; model must be Korean and depends on manufacturer; sort enumerates the accepted literal values where the schema declares no enum; maxItems is described with its billing implication. The gap is that the schema defaults (sort='newest', maxItems=20) are never restated, so an agent must open the schema to learn them.

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 Korean used-car listings') and pins the source to KB Chachacha, KB Financial's marketplace, which separates it from sibling listing tools like encar_listings or passo_motorcycles. It also enumerates the returned fields, so an agent immediately knows the shape of the payload.

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?

The Args section gives per-filter semantics ('Empty = all', model 'requires manufacturer'), which implies a filtered-listing use case, but there is no explicit statement of when to choose this tool over encar_listings or danawa_prices, nor any exclusion. Usage is inferable rather than stated.

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