Skip to main content
Glama
Sign In
naver-land-mcp

naver-land-mcp

by kimduksoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_complex_detail

Get detailed information on a housing complex: households, area, occupancy year, and construction company. Provide the complex code to receive the data.

Instructions

단지 상세 정보 (세대수, 면적, 입주년도, 건설사 등)

Args: complex_no: 단지 코드

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": {
      "complex_no": "<complex_no>"
    },
    "name": "get_complex_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
complex_noYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only lists the parameter and example fields but fails to disclose behavioral traits such as whether the operation is read-only, requires authentication, or has rate limits. The description is minimal.

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

Conciseness3/5

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

The description is short, containing both Korean and English text. It is mostly concise, but the parameter description is redundant with the schema. It could be more streamlined.

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?

Given that an output schema exists, the description does not need to explain return values. The tool has only one parameter and the description covers its purpose. However, due to the lack of behavioral transparency and usage guidelines, the description is minimally complete.

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

Parameters2/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 add meaning. It provides 'complex_no: 단지 코드' (complex code) which is a minor addition, but does not explain the format or source of the code. The description adds limited value beyond the 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?

The description clearly states '단지 상세 정보' (complex detail info) and lists example fields (households, area, move-in year, construction company). It distinguishes from siblings like 'get_complexes' which likely lists complexes, and 'get_price_info' etc.

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 usage for retrieving detailed info for a specific complex, but provides no explicit guidance on when to use this tool vs alternatives, nor any exclusions or prerequisites.

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

Deploy Server

Other Tools