Skip to main content
Glama

APICK Business

상가·오피스텔 기준시가

std_price_commercial
Read-only

Look up the official standard price of a commercial building unit or officetel in Korea by address. 주소(지번·도로명) 또는 법정동코드+번지로 기준시가(㎡당 고시가격)·전용면적·호별 기준시가·고시일자를 조회합니다. unit_no(호실 번호)를 함께 보내면 해당 호실만, 없으면 최대 50건 목록을 돌려주며, 고시되지 않은 지역은 count 0으로 응답합니다. [호출당 50포인트]

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": "std_price_commercial"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoNo지번의 호(부번지). 건물을 특정할 때 씁니다.
jiNo번지 (예: 431). address 대신 dong과 함께 직접 보낼 수 있습니다.
dongNo법정동코드 10자리. address 대신 ji와 함께 직접 보낼 수 있습니다.
addressNo지번 또는 도로명 주소 (예: 서울특별시 동대문구 장안동 123) — dong·ji를 주지 않으면 필수
unit_noNo호실 번호 (예: 101). 보내면 해당 호실만 돌려줍니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses concrete behavioral facts: an unqualified query returns at most 50 records, sending unit_no collapses the result to one unit, unannounced districts return count 0 rather than an error, and each call costs 50 points. The cost and empty-result semantics are exactly the kind of operational context annotations cannot convey.

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?

Purpose is front-loaded in English, with Korean detail following, and every clause carries information (fields returned, 50-record cap, count 0, point cost). The English and Korean sentences partially duplicate the address/unit_no rules, which is a minor redundancy rather than bloat.

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?

There is no output schema, and the description compensates well by naming the returned fields and the empty-result shape. The one gap is what happens past the 50-record cap — no offset/cursor parameter exists and the description does not say how to retrieve further results.

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 100%, so the baseline is 3, but the description adds meaning the schema lacks: the effect of unit_no (single-unit vs up-to-50 list) and the address-vs-dong+ji exclusivity. It does not explain the ho (부번지) parameter's interaction with ji, which remains schema-only.

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 first sentence gives a specific verb and resource ('look up the official standard price of a commercial building unit or officetel in Korea'), and the Korean sentence enumerates the exact fields returned (㎡당 고시가격, 전용면적, 호별 기준시가, 고시일자). This clearly separates it from land-oriented siblings such as land_rt_price without needing the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the two input routes — a jibun/road-name address, or 법정동코드 + 번지 — and states that unit_no narrows the result to a single unit versus a list. It does not explicitly contrast with land_rt_price or other price tools, so the agent must infer the commercial-vs-land boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.