Skip to main content
Glama

Jaryo - Korean company records, sourced. Start with verify_company (no key)

Verify a Korean company

verify_company
Read-only

Start here. Verify a Korean corporation by name, business registration number (10 digits), corporate registration number (13 digits), DART code (8 digits) or stock code (6 digits): does it exist, its National Tax Service status (active / suspended / closed, with the date it was checked), official numbers, Korean and English names, address, industry and sources. Up to 10 matches, best-known company first; more_matches=true means add the business number or city to narrow. Each match has match_type and former_names (previous names; match_type former_name when the query equals only one of them); name results also have rank_reason (why it is in that place) and the response has ranking. industry.ko / industry.en are official KSIC names (11th revision); industry.tax_business_type is a tax classification, not KSIC. Corporations only — individual businesses are answered as not supported. No scores or judgements. No key needed. (한국 법인 확인)

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": {
      "q": "<q>"
    },
    "name": "verify_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCompany name (Korean or English), business registration number / 사업자등록번호 (10 digits), corporate registration number / 법인등록번호 (13 digits), DART corp code (8 digits) or stock code (6 digits)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Company name, 사업자등록번호 (10 digits), 법인등록번호 (13 digits) or stock code (6 digits)"New value: +"Company name (Korean or English), business registration number / 사업자등록번호 (10 digits), corporate registration number / 법인등록번호 (13 digits), DART corp code (8 digits) or stock code (6 digits)"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say readOnly and openWorld; the description adds real operational context: a 10-match cap with a narrowing strategy, no key required, corporations-only scope with an explicit 'not supported' outcome for individual businesses, and 'no scores or judgements' so the agent knows results carry no ranking opinion. It also explains what NTS status values mean and how they are dated.

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 action and scope, then organized by identifier types and response fields. It is dense and somewhat run-on, packing output documentation into one long sentence-chain, but nearly every clause carries information the agent needs.

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?

With no output schema, the description takes on the burden of explaining return fields and does so thoroughly (match_type, former_names, rank_reason, ranking, industry KSIC vs tax classification). For a single-parameter read-only lookup, nothing material 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 coverage is 100% and the schema already enumerates every accepted identifier format with digit counts, so the description largely restates it. It adds little new meaning to 'q' beyond confirming Korean/English name input, which the schema also states; 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+resource ('Verify a Korean corporation') and enumerates the five identifier formats it accepts, plus exactly what is returned (existence, NTS status, names, address, industry, sources). The leading 'Start here' also signals its role as the entry point relative to siblings like get_company or resolve_company.

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?

'Start here' gives clear entry-point guidance, and 'more_matches=true means add the business number or city to narrow' tells the agent how to recover from an ambiguous result. It stops short of naming an explicit alternative tool for enrichment or of stating when not to use this one, so it is clear context without full when/when-not coverage.

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.