Skip to main content
Glama

토지 정보

get_land_info
Read-onlyIdempotent

경매 사건번호를 주면 물건 필지별 공시 토지특성을 돌려준다 — 지목·이용상황·용도지역·도로접면·지세·형상·면적(㎡·평)·공시지가(㎡당)와 최근 연도별 변동. 땅·임야·농지·단독주택 질문에 쓴다. 공시지가는 시세가 아니고 소유자 정보는 주지 않는다.

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": {
      "case_no": "<case_no>"
    },
    "name": "get_land_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNo법원명
case_noYes사건번호
item_noNo물건번호

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: the official land price is explicitly not a market price, owner information is explicitly out of scope, and the granularity is per-parcel with year-by-year change history. That prevents two plausible misinterpretations of the returned data.

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?

Three sentences, front-loaded with the input-to-output contract, then use cases, then caveats. The field enumeration is dense but each item is informative and none reads as filler. Slightly list-heavy, but no sentence is wasted.

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?

With no output schema, the description carries the burden of describing the return value, and it does so by enumerating the returned attributes plus the per-year change series. Scope limits (no owner data, price is assessed not market) are stated. The residual gap is how multi-parcel results are shaped and what item_no does.

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?

Schema description coverage is 100%, so all three parameters are already documented in the schema, and the standard baseline is 3. The description only signals that the case number is the driving input; it adds nothing about court or item_no semantics, such as whether item_no selects a single parcel among several.

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 opens with a specific verb-plus-resource: given an auction case number it returns publicly assessed land characteristics per parcel, and it enumerates the concrete fields (land category, zoning, road adjacency, terrain, shape, area, official price, yearly change). This is far more specific than the title '토지 정보'. It does not explicitly separate itself from the sibling get_location, so it stops short of a 5.

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?

It states the question types that select this tool — land, forest, farmland, detached house queries. What is missing is the negative side: no statement of when NOT to use it (e.g., for apartment or building questions) and no named alternative among the large sibling set.

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.

Resources