Skip to main content
Glama

법인 등기 검색

registry_corporate_search
Read-only

Find corporate registry targets in Korea by 13-digit corporate registration number or 10-digit business number. 법인등록번호 또는 사업자등록번호로 법인 등기 대상을 찾습니다. 개인사업자·미등록이면 결과가 없으며, 검색이 정상으로 끝났으면 결과가 없어도 40P가 차감됩니다. [호출당 40포인트]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "registry_corporate_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
biz_noNo사업자등록번호 10자리(하이픈 제외). corp_reg_no가 없을 때 사용
corp_reg_noNo법인등록번호 13자리(하이픈 제외)

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 declare readOnlyHint and openWorldHint, so the description's job is to add cost and outcome context — and it does: 40 points per call, charged even when a normally completed search returns nothing. That billing-on-empty-result warning is exactly the kind of non-obvious behavior an agent needs. It does not describe what a successful result contains or whether the two IDs can be combined.

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?

Short and front-loaded: purpose first, then the negative-result caveat, then cost. The Korean text is largely a restatement of the English sentence rather than added information, which is mild redundancy but defensible for a bilingual audience.

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 two-optional-parameter read-only lookup with a fully documented schema, the description covers the crucial gaps: which identifiers qualify, what happens on no match, and the 40-point charge. The remaining gap is return-content expectations, which matters somewhat given there is no 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?

Schema description coverage is 100% and the schema already explains the 10-digit/13-digit patterns and that biz_no is used when corp_reg_no is absent. The description restates the digit counts but adds no new meaning about precedence, mutual exclusivity, or providing both. Baseline 3 is appropriate.

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 ('Find corporate registry targets in Korea') plus the exact identifier formats accepted (13-digit corporate registration number, 10-digit business number). This separates it in kind from sibling lookups like registry_realestate_search or registry_doc_verify, though no sibling 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 Guidelines3/5

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

It does establish a negative condition — sole proprietors (개인사업자) and unregistered entities return no results — which tells the agent when the tool will be fruitless. However, there is no guidance on when to choose this over the registry/geo/dart siblings, and the corp_reg_no vs biz_no priority is only implied by the schema, not the description.

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.