kakao-mcp

kakao_coord_to_region

Convert longitude and latitude coordinates to administrative district information, identifying the legal dong and administrative dong for a location. Get region data from coordinates.

Instructions

위경도 좌표를 행정동/법정동 행정구역 정보로 변환.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "kakao_coord_to_region"
  }
}

Input Schema

Name	Required	Description	Default
`x`	Yes	경도(longitude)
`y`	Yes	위도(latitude)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the conversion action without detailing coordinate system assumptions, error handling, or any operational constraints. An agent gets no additional behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, compact Korean sentence that is front-loaded and directly states the tool's purpose. It contains zero unnecessary words and achieves high information density.

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

Completeness3/5

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

For a simple two-parameter conversion tool, this description is adequate for understanding the core purpose. However, without an output schema or explanation of the exact fields in '행정동/법정동 행정구역 정보', an agent may lack enough context to parse the returned response fully.

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

Parameters3/5

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

The schema already describes x as longitude and y as latitude with 100% coverage. The description's mention of '위경도 좌표' adds minimal extra meaning beyond the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a conversion action ('위경도 좌표를 ... 변환') with a specific resource type (행정동/법정동 행정구역 정보). It doesn't explicitly differentiate from the sibling 'kakao_coord_to_address', but the output specificity makes it distinct enough.

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 description implies a use case for converting coordinates to administrative region info but provides no explicit guidance on when to use this tool versus the sibling 'kakao_coord_to_address'. No alternatives or exclusions are mentioned.

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

Deploy Server