Skip to main content
Glama

통신판매업 신고 조회

ecommerce_registration
Read-only

Look up every e-commerce (mail-order) business registration filed by a Korean business: registration number, trade name, representative, operating status, filing date, filing office and address. Active registrations come first. 사업자등록번호로 통신판매업 신고 이력 전부(신고번호·상호·대표자·운영상태·신고일자·신고기관·소재지)를 조회합니다. 정상영업 신고가 앞에 오며, 이력이 없으면 count 0 이고 이때도 정상 조회로 과금됩니다. [호출당 10포인트]

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": {
      "biz_no": "<biz_no>"
    },
    "name": "ecommerce_registration"
  }
}

Input Schema

NameRequiredDescriptionDefault
biz_noYes사업자등록번호 10자리 (하이픈 포함 가능, 예: 1234567890)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond them: results are ordered with active registrations first, an empty history returns count 0 yet is still treated as a successful lookup and still billed, and each call costs 10 points. Those are exactly the cost/edge-case disclosures an agent needs before calling; only the exact shape of the response payload is left unspecified.

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?

The content is front-loaded and the billing warning is well placed at the end. However, the entire field list and scoping statement are duplicated in Korean with no new information, roughly doubling the length of a one-parameter lookup tool. The bilingual restatement is the main structural inefficiency.

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?

For a single-parameter, side-effect-free lookup with no output schema, the description supplies everything needed to call it correctly: the input identity, the returned fields, result ordering, the empty-result semantics and the per-call cost. Nothing material about invocation is left to guesswork.

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% and the single biz_no parameter is already documented with a 10-digit format and hyphen tolerance, so the baseline is 3. The description's 'Korean business' / 사업자등록번호 phrasing adds no format or normalization detail beyond what the schema states, and it does not say how a non-Korean or malformed number is handled.

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 definition pairs a specific verb ('Look up every e-commerce (mail-order) business registration') with an explicit scope ('filed by a Korean business') and enumerates the returned fields (registration number, trade name, representative, operating status, filing date, office, address). That is far more specific than a restated name. It never names a sibling such as biz_detail or corp_finance, so an agent must still infer why it should pick this tool over related Korean corporate-data lookups.

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?

Usage is implied rather than stated: the agent can infer it should call this when it holds a 사업자등록번호 and needs 통신판매업 filing history. There is no explicit when-not guidance and no named alternative for adjacent needs (e.g., general business registration details). The billing note adds a useful decision input but is not a routing rule.

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.