Skip to main content
Glama

지방세 납세증명서 발급

gov24__local_tax_certificate__issue
Destructive

REQUIRES prior gov24__session__login call with same account_link_id. 지방세 납세증명서를 발급하고 내려받는 링크를 돌려줍니다. pre_consent 는 true 여야 합니다. 이 도구는 기관의 기록을 바꿉니다. 첫 호출은 실행되지 않고, 전송할 내용의 미리보기와 1회용 confirmation_token 을 돌려줍니다(오류 WRITE_CONFIRMATION_REQUIRED). 그 미리보기를 사용자에게 그대로 보여 줍니다. 사용자가 동의한 뒤에만 같은 인자에 그 confirmation_token 을 더해 다시 호출합니다. 사용자의 동의 없이 토큰을 넣지 않습니다. 인자를 하나라도 바꾸면 토큰은 무효가 됩니다. 그때는 토큰 없이 호출해 새 미리보기를 받습니다. Files: the document the institution issued, unchanged, as PDF, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

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": {
      "phone": "<phone>",
      "business_address": "<business_address>",
      "certificate_purpose": "<certificate_purpose>",
      "receive_method": "<receive_method>",
      "pre_consent": "<pre_consent>"
    },
    "name": "gov24__local_tax_certificate__issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYesContact number, split the way the institution form takes it.
member_typeNoOptional. Member kind.
pre_consentYesMust be true. Confirms the prior consent.
receive_methodYesDelivery code.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
business_addressYesWorkplace address as the institution address finder returns it.
payment_recipientNoOptional. Named recipient other than the taxpayer.
confirmation_tokenNo첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.
other_purpose_textNoOptional. Required when certificate_purpose is 99.
certificate_purposeYesStated purpose code. 99 needs other_purpose_text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, it discloses that the first call is a dry run returning a preview plus a one-time token (WRITE_CONFIRMATION_REQUIRED), that the token expires in 10 minutes and is single-use, and that changing any argument invalidates it. It also explains that each call consumes a token, creates an XBOSS job, and that files are kept 7 days with 15-minute download URLs, which is exactly the operational context annotations cannot carry.

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 precondition and the confirmation flow are front-loaded correctly, but the text is bloated by a long mixed Korean/English passage on anonymous recovery_receipt handling that reads as generic platform boilerplate rather than guidance specific to issuing this certificate. Language switches mid-paragraph and the receipt paragraphs dilute the actionable core.

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?

With 10 parameters, nested objects, and no output schema, the description does the necessary work of describing the return payload (artifacts[] with download_url and retention windows) and the fallback path for expired links. It is nearly complete, but the recovery_receipt section is dense and does not clearly map to a parameter or result field of this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds real semantic rules the schema does not state: pre_consent must be true, and any argument change between the preview call and the confirmation call invalidates confirmation_token. The account_link_id linkage requirement is also restated with the login dependency, though that is partially duplicated from the schema.

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: it issues a local tax payment certificate (지방세 납세증명서) and returns a download link, which matches the title and the tool name. It does not name or contrast itself with the sibling certificate-issuing tools (gov24__business_registration_certificate__issue, hometax__certificate__apply__*), so an agent must infer that boundary from the resource name alone.

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?

It states concrete preconditions (prior gov24__session__login with the same account_link_id, pre_consent must be true) and the exact two-call confirmation protocol, including what to do when arguments change. It also routes expired links to xdata__job__result by job_id. It stops short of stating when to prefer this over the other certificate-issuing siblings.

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.

Resources