Skip to main content
Glama

부동산 등기 검색

registry_realestate_search
Read-only

Find real estate registry targets in Korea by road/lot address or 14-digit property number. 주소 또는 부동산고유번호로 등기부등본 열람·발급 대상을 찾습니다. 특정 대상을 발급하려면 결과 targets의 pin(부동산고유번호)을 registry_realestate_jobs_create에 전달하세요. 결과가 없어도 검색이 정상으로 끝나면 40P가 차감되고, 실패하면 0P입니다. [호출당 40포인트]

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": {
      "query": "<query>"
    },
    "name": "registry_realestate_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes주소(도로명·지번) 또는 부동산고유번호 14자리

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so cost behavior is uncontested extra value: 40 points are billed per call even on a zero-result but successful search, while a failure bills 0. This is exactly the kind of non-obvious trait the description should carry. It does not discuss rate limits or result-count caps.

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?

The definition is front-loaded with the purpose and then adds the downstream step and cost rule in short clauses. The bilingual Korean/English restatement is slightly redundant, but each sentence still carries a distinct operational fact.

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?

For a single-parameter search tool with no output schema, this covers the essentials: the two accepted input forms, the downstream handoff and pin field, and the billing rule. The description even describes the shape of results (targets with pin), which partially compensates for the missing output schema.

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?

There is only one parameter and the schema describes it fully (2-120 chars, address or 14-digit property number). The description repeats the same format information rather than adding syntax examples or disambiguation between the two input modes. A baseline 3 is appropriate because coverage is 100%.

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 definition opens with a specific verb and resource ('Find real estate registry targets in Korea') and scopes the lookup to road/lot address or a 14-digit property number. This is distinguishable from the corporate and document-verification siblings, and the follow-up tool registry_realestate_jobs_create is named explicitly.

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 makes the workflow explicit: use this to locate a target, then pass the resulting targets' pin into registry_realestate_jobs_create to issue a document. It also flags the empty-result case, which is the main ambiguity. It stops short of naming when an alternative search tool should be used instead.

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.