Skip to main content
Glama

주변 위험·규제

get_nearby_risks
Read-onlyIdempotent

경매 사건번호를 주면 물건 주변 위험·규제를 돌려준다 — 가장 가까운 송전선(전압·거리)·필지 안 철탑 추정·변전소·발전소, 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_nearby_risks"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNo법원명
case_noYes사건번호. 예: '2025타경1129'
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=true, openWorld=false, idempotent=true and destructive=false, so safety and determinism are covered. The description adds real value beyond that: it discloses which data sources are queried and, critically, that 'not in list' means 'not found in that source' rather than 'safe' — an interpretive caveat an agent could not infer from the annotations. It stops short of describing pagination, latency, or failure behavior, so not a 5.

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?

Front-loaded with the verb-resource-core, then a dense dash-separated inventory that maps one-to-one onto the returned data classes, ending with the interpretation caveat. Every clause carries content, though the single run-on sentence is heavy and could be split for scanability.

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 full burden of explaining return values and does so thoroughly, including the negative-result caveat that prevents a dangerous misreading. Remaining gaps are minor: no note on what happens when the case number is unknown or on how optional<court/item_no> affect lookup, but an agent has enough to call it correctly.

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% — court ('법원명'), case_no with a concrete example ('2025타경1129'), and item_no ('물건번호') are all documented in the schema. The description only signals that case_no is the driving input and says nothing about when court or item_no are needed for disambiguation, so it neither compensates nor adds materially. Baseline 3 applies.

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?

States a specific verb and resource ('경매 사건번호를 주면 물건 주변 위험·규제를 돌려준다') and then enumerates the exact contents returned — nearest transmission line with voltage/distance, pylon estimate, substation, evasive facilities within 2km by type and count, regulation zones, maintenance/district-unit plan area membership, non-water-supply area. This is far more specific than the sibling names get_case or search_auctions and lets an agent tell immediately what data class it gets.

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 establishes the input contract (an auction case number) and thus implies when the tool applies, and the closing caveat guides interpretation of results. But it never states when to prefer this over siblings such as get_case or get_sale_probability, nor any preconditions or exclusions.

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