Skip to main content
Glama
korea-data-mcp

korea-data-mcp

by parkseokjune

naver_place

Search Korean local businesses on Naver Place and get clean English JSON with name, category, phone, address, hours, rating, and reviews for any Korean or English search phrase.

Instructions

Search Naver Place (Korea's dominant local-business map, since Google Maps is permanently crippled inside Korea by map-data export law) and return Korean local businesses as clean English JSON: name, category, phone, address, opening hours, rating, and reviews.

Args: searchQuery: Korean or English search phrase, e.g. "강남역 카페" (Gangnam Station cafes). Required. maxPlaces: Maximum number of places to return. includeReviews: Whether to include reviews for each place. maxReviewsPerPlace: Maximum reviews to fetch per place.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "searchQuery": "<searchQuery>"
    },
    "name": "naver_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxPlacesNo
searchQueryYes
includeReviewsNo
maxReviewsPerPlaceNo

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?

No annotations exist, so the description carries the disclosure burden. It adds useful context (returns clean English JSON, Korea-specific because Google Maps data export is restricted) but omits rate limits, auth requirements, and error/empty-result behavior.

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 purpose sentence followed by a clean Args list mapping each parameter. The Google Maps parenthetical adds rationale at modest length without derailing the core instruction.

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?

An output schema exists so return values needn't be re-explained, and all four parameters are documented. The only gaps are operational details like pagination and error handling, which are minor for a read-only search tool.

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 coverage is 0%, so the description must compensate, and it does document all four parameters with meaning (searchQuery is Korean/English and required; maxPlaces, includeReviews, maxReviewsPerPlace described). It does not restate the schema defaults, but the semantics are clear.

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 ('Search') and resource ('Naver Place') and clarifies it returns Korean local businesses with the exact fields returned (name, category, phone, address, hours, rating, reviews). This is clearly distinguishable from the shopping/ranking siblings in the catalog.

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?

Provides an example query ('강남역 카페') and notes Korean or English input, which implies appropriate usage, but there is no explicit when-to-use/when-not guidance or naming of alternatives. 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.