Skip to main content
Glama

국세 증명서 원본 확인

tax_cert_verify
Read-only

Verify a Korean tax certificate by the issuance number printed on it. 증명서에 인쇄된 발급번호(14자리)와 등록번호(주민 앞 6자리·사업자 10자리)로 납세증명서·소득금액증명·사업자등록증명 등 발급 사실을 확인합니다. 확인 결과는 verified(true 발급 사실 확인, false 발급 이력 없음)로 응답하며 증명서 원문은 돌려주지 않습니다. [호출당 40포인트]

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": {
      "cert_no": "<cert_no>",
      "txpr_no": "<txpr_no>"
    },
    "name": "tax_cert_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
cert_noYes증명서의 발급번호 14자리. 연계문서는 첫 자리 T (예: 20260101123456)
txpr_noYes등록번호 — 주민등록번호 앞 6자리(개인) 또는 사업자등록번호 10자리
txpr_clsfNo납세자 구분. 01 개인 02 사업자 (기본: 등록번호 길이로 자동 판정)

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 cover the read-only and open-world profile, and the description adds real value beyond them: the response shape (verified true = issuance confirmed, false = no issuance history), the fact that the document body is never returned, and a per-call cost of 40 points. It omits what happens on invalid or malformed numbers or rate limits, so it stops short of 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?

Three sentences, front-loaded with the core action, then scope, then return semantics and cost. The English lead sentence followed by Korean detail is slightly redundant but each sentence carries distinct information, and nothing is padding.

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 3-parameter read-only lookup with no output schema, the description supplies what the schema cannot: the meaning of the boolean result and the absence of document text. Cost disclosure further rounds it out; only error behavior is left unstated.

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%, so the baseline is 3. The description restates the issuance-number length and the resident/business registration number formats already documented in the schema, adding no new format, example, or edge-case guidance beyond it.

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 ('Verify a Korean tax certificate') plus the exact identifying input (issuance number printed on it). It also lists the certificate types in scope and clarifies that the document text is not returned, which implicitly separates it from the bundle-retrieval siblings. It falls short of a 5 because it never names an alternative tool.

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: call this when you need to confirm that a certificate was actually issued, and expect only a true/false answer. The statement that the original document is not returned hints that document retrieval belongs to another tool, but no alternative or exclusion is stated explicitly. The 40-point cost note is a useful usage consideration.

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.