Skip to main content
Glama

전자세금계산서 발급사실 확인

tax_invoice_third_party_check
Read-only

Verify the issuance of a Korean electronic tax invoice or e-statement (제3자 발급사실 조회). 공급자 사업자등록번호·공급받는자 등록번호·승인번호·작성일자·공급가액으로 전자세금계산서·전자계산서 발급 사실을 확인합니다. 확인 결과는 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": {
      "splr_no": "<splr_no>",
      "dmnr_no": "<dmnr_no>",
      "etan": "<etan>",
      "wrt_dt": "<wrt_dt>",
      "sum_amt": "<sum_amt>"
    },
    "name": "tax_invoice_third_party_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
etanYes승인번호(24자리 이상, 공백·하이픈 제거 후 사용)
wrt_dtYes작성일자 YYYYMMDD
dmnr_noYes공급받는자 등록번호 — 사업자 10자리 또는 주민 13자리
splr_noYes공급자 사업자등록번호 10자리
sum_amtYes공급가액(원, 숫자만)

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?

Beyond the readOnlyHint=true and openWorldHint=true annotations, the description adds genuinely useful behavior: the result is a boolean 'verified' field (true = issuance confirmed, false = no issuance history) and the original document text is deliberately not returned. It also discloses a per-call cost of 40 points, which is material for an agent deciding whether to invoke it.

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?

The definition is short and front-loaded, leading with the English verb phrase before the Korean detail. There is mild redundancy in restating the parameter list already covered by the schema, but nothing is padded or wasteful.

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?

There is no output schema, so the description carries the return-value burden and does so by naming the 'verified' boolean, its true/false meaning, and the absence of raw source text. Combined with the disclosed point cost, an agent has enough to call and interpret it; only failure/timeout behavior is unaddressed.

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 five required parameters (supplier number, recipient number, approval number, write date, supply amount) are already documented with formats and patterns. The description merely enumerates the same fields in Korean without adding syntax, ordering, or matching semantics such as whether all five must correspond to the same invoice.

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 description gives a specific verb and resource: verify the issuance of a Korean electronic tax invoice/e-statement, scoped to third-party lookup (제3자 발급사실 조회). It is clear what the tool does, but it never differentiates itself from the similarly named sibling tax_cert_verify, so an agent must infer the boundary from the resource noun alone.

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 Korean sentence lists the identifiers needed to run the check, which hints at the use case (verify whether a specific invoice was actually issued). There is no explicit when-to-use / when-not-use guidance and no named alternative, so routing between this and related tax tools is left to inference.

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.