Skip to main content
Glama

입지

get_location
Read-onlyIdempotent

경매 사건번호를 주면 경매레이더 입지 판정을 돌려준다 — 전철역(1.2km)·학교(도보권 초중고)·학원가·공공기관·병원·버스정류장·기피시설·상가·편의시설의 판정 문장과 가까운 곳(이름·직선거리). '역세권이야?', '학교 가까워?' 같은 질문에 쓴다.

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_location"
  }
}

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral content beyond that: the input unit is 경매 사건번호, the assessment covers nine named facility categories, and the subway criterion is explicitly 1.2km with others expressed as 도보권/직선거리. It omits what happens when the case has no data or the case number is invalid.

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?

Two sentences, both earning their place: the first is front-loaded with the action and output inventory, the second gives trigger phrasing. The long parenthetical category list is dense but is the core value proposition, not filler. Slightly list-heavy phrasing keeps it from a 5.

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 return-value burden and does so well by describing both the 판정 문장 and the 가까운 곳 (name plus straight-line distance) shapes. It also discloses the 1.2km radius that frames the answers. Only the error/empty-result case and any cost or latency characteristics are left unaddressed.

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 court, case_no and item_no are each documented in the schema, and the description only reinforces that case_no is the auction case number. It adds no guidance on when to supply court or item_no, or how they disambiguate a case. Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb and resource ('경매 사건번호를 주면 ... 입지 판정을 돌려준다') and enumerates exactly which judgment categories come back (전철역, 학교, 학원가, 병원, 기피시설 등). An agent knows precisely what it gets. It does not name a sibling such as get_nearby_risks, which overlaps on 기피시설, so differentiation is not fully resolved.

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?

Gives concrete trigger questions ('역세권이야?', '학교 가까워?') that map directly onto when to call this tool, which is stronger than a generic 'use for location info'. It does not say when NOT to use it or which sibling to prefer for overlapping risk/facility queries, so the routing guidance is incomplete rather than absent.

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