Skip to main content
Glama

BOIM Korea Vendor Directory

동네 간판·인쇄·광고물 가게 찾기

find_local_shops
Read-onlyIdempotent

Find neighborhood sign, advertising, print and copy shops in a Korean city, district or dong (public store data; name order, not a ranking). [보임 — 한국 업체·입찰 공고 찾기] 소상공인 상가정보(소상공인시장진흥공단, 공공데이터)에 등록된 동네 가게를 시·군·구·동으로 찾습니다. 간판·광고물 제작, 광고물 디자인, 옥외·전시 광고, 명함·인쇄, 복사·출력. 개인·소규모 일(가게 간판, 현수막, 인쇄물, 출력)을 맡길 곳을 물을 때 쓰세요. 상호·업종·행정동만 있고 실적·연락처는 없으며 순서는 이름순입니다(평가 아님). 업체가 직접 등록해 국세청 확인을 거친 곳은 registered_card로 업체 카드 URL이 붙습니다. 조달 실적이 있는 업체는 search_vendors를 쓰세요.

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": {
      "region": "<region>"
    },
    "name": "find_local_shops"
  }
}

Input Schema

NameRequiredDescriptionDefault
workNo하는 일: 간판, 광고물 디자인, 옥외 광고, 인쇄물, 복사·출력
limitNo보여 줄 최대 건수(1~50). 결과가 이보다 많거나 공개 한도(5건)를 넘으면 나머지는 결과의 not_shown 수와 more 주소로 알려 줍니다
queryNo상호에 들어간 말
regionYes시·도, 시·군·구 또는 행정동(예: 세종, 대전 유성구, 보람동)

Output Schema

NameRequiredDescriptionDefault
citeNo답에 붙일 출처 한 줄
moreNo나머지를 볼 보임 웹 목록 주소(누구나 열람)
noteNo조건 풀이·안내
workNo알아들은 하는 일
errorNo실패 사유(isError일 때만)
orderNo순서 기준(관련도·이름순 등 — 평가·순위 아님)
shownNo이번에 보인 수
totalNo조건에 맞는 전체 수
sourceNo자료 출처
resultsNo결과 줄(한 번에 5건까지)
registerNo업체 무료 등록 안내 주소
not_shownNo보이지 않은 나머지 수(있을 때)
data_as_ofNo자료 기준일

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"보여 줄 최대 건수(1~50). 결과가 이보다 많거나 공개 한도(5건)를 넘으면 나머지는 결과의 not_shown 수와 more 주소로 알려 줍니다"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "cite": {
      +      "description": "답에 붙일 출처 한 줄"
      +    },
      +    "data_as_of": {
      +      "description": "자료 기준일"
      +    },
      +    "error": {
      +      "description": "실패 사유(isError일 때만)"
      +    },
      +    "more": {
      +      "description": "나머지를 볼 보임 웹 목록 주소(누구나 열람)"
      +    },
      +    "not_shown": {
      +      "description": "보이지 않은 나머지 수(있을 때)"
      +    },
      +    "note": {
      +      "description": "조건 풀이·안내"
      +    },
      +    "order": {
      +      "description": "순서 기준(관련도·이름순 등 — 평가·순위 아님)"
      +    },
      +    "register": {
      +      "description": "업체 무료 등록 안내 주소"
      +    },
      +    "results": {
      +      "description": "결과 줄(한 번에 5건까지)",
      +      "items": {
      +        "properties": {
      +          "area": {
      +            "description": "시군구·행정동"
      +          },
      +          "list_page": {
      +            "description": "그 동네·업종 목록 주소"
      +          },
      +          "name": {
      +            "description": "상호"
      +          },
      +          "registered_card": {
      +            "description": "업체가 직접 등록한 업체 카드 주소(있을 때)"
      +          },
      +          "work": {
      +            "description": "하는 일"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "shown": {
      +      "description": "이번에 보인 수"
      +    },
      +    "source": {
      +      "description": "자료 출처"
      +    },
      +    "total": {
      +      "description": "조건에 맞는 전체 수"
      +    },
      +    "work": {
      +      "description": "알아들은 하는 일"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / work / description
      Previous value: -"하는 일: 간판, 광고물 디자인, 옥외 광고, 인쇄(명함), 복사·출력"New value: +"하는 일: 간판, 광고물 디자인, 옥외 광고, 인쇄물, 복사·출력"
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/closed-world, so the description focuses on what the data actually contains: source (소상공인 상가정보 공공데이터), the absence of 실적·연락처, name-order results that are explicitly not a ranking, and the registered_card URL appearing only for 국세청-verified self-registered shops. Minor gap: pagination behavior only lives in the schema's limit description, not here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with a usable English summary, but the body is bilingual duplication: 'name order, not a ranking' is restated as '순서는 이름순입니다(평가 아님)', and the bracketed tag '[보임 — 한국 업체·입찰 공고 찾기]' is internal noise for an agent. The extra text is defensible but not tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers source, coverage limits, what is and isn't returned, ordering semantics, the registered_card field, and the alternative tool — with an output schema and rich annotations covering return structure and safety. Nothing needed to call it correctly is missing.

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 four parameters are already documented with examples (region '세종, 대전 유성구, 보람동'; work types). The description reinforces the field axes ('상호·업종·행정동만 있고') but adds no syntax or semantics beyond what the schema supplies, so the baseline 3 is right.

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+resource (find neighborhood sign/advertising/print shops) and pins the scope to Korean administrative units (시·군·구·동). It explicitly distinguishes itself from the sibling search_vendors for businesses with procurement records, so the agent can route without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit use case ('개인·소규모 일 — 가게 간판, 현수막, 인쇄물, 출력 — 을 맡길 곳을 물을 때') and an explicit exclusion routing to search_vendors for 조달 실적 vendors. The alternative is named with the condition that selects it.

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.