Skip to main content
Glama
korea-data-mcp

korea-data-mcp

by parkseokjune

passo_motorcycles

Fetch Korean used-motorcycle listings from Passo with brand, year, price, and sort filters applied server-side, so you receive only matching bikes and pay per listing.

Instructions

Return Korean used-motorcycle listings from Passo (~11,000 live): brand_en, model, year, price_krw, mileage_km, region_province_en, photo and URL. Filters run on Passo's own server, so only matching listings are fetched and billed.

Args: maker: Brand in English or Korean, e.g. "Honda", "Harley-Davidson". Empty = all. yearFrom: Earliest model year, or 0 for no limit. yearTo: Latest model year, or 0 for no limit. priceMinKrw: Minimum price in KRW, or 0 for no limit. priceMaxKrw: Maximum price in KRW, or 0 for no limit. sort: "newest", "price_asc", "price_desc", "year_desc", "year_asc", "mileage_asc" or "mileage_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": "passo_motorcycles"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNonewest
makerNo
yearToNo
maxItemsNo
yearFromNo
priceMaxKrwNo
priceMinKrwNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/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 real behavior: server-side filtering, per-listing billing, and a maxItems cap that controls cost. It omits auth requirements, rate limits, and error/empty-result behavior, keeping it short of a 5.

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 lead sentence is front-loaded with purpose and return fields, and the Args block is scannable. The dense field list in sentence one is slightly heavy but every element is informative, so there is little waste.

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 seven-parameter, zero-required listing tool with an output schema, the description covers filtering semantics, sorting, cost control, and result shape. Only minor gaps remain, such as the default for maxItems and sort, which the schema supplies anyway.

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?

Schema coverage is 0%, yet the description documents all seven parameters: maker accepts English or Korean with examples, the year/price bounds explain that 0 means no limit, sort enumerates every allowed value, and maxItems ties to billing. This fully compensates for the bare 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?

States a specific verb and resource ('Return Korean used-motorcycle listings from Passo'), quantifies the inventory (~11,000 live), and enumerates the returned fields, so an agent knows exactly what it gets and can distinguish it from the other marketplace siblings.

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?

It explains an important operational condition — filters run server-side so only matching listings are fetched and billed — which implicitly tells the agent to filter rather than fetch broadly. However, there is no explicit when-to-use/when-not guidance or named alternative for overlapping needs.

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