Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

전자세금계산서 수정

hometax__etax__invoice__modify
Destructive

REQUIRES prior hometax__session__login call with same account_link_id. Issue a correcting e-tax invoice (수정세금계산서) against an existing one. IRREVERSIBLE, same as issuing: call without confirm first to get a preview, show it to the user, then retry with confirm=true. You MUST ask the user which correction reason applies and pass etxiv_mdf_rsn_cd; never guess it. 호출마다 토큰 1소진

Input Schema

NameRequiredDescriptionDefault
confirmNoSet true ONLY after showing the preview to the user and receiving their explicit approval.
old_aprv_noYesApproval number of the original invoice (원본 승인번호, 24 digits; hyphens allowed). Get it from hometax__etax__invoice__search_list.
supply_dateYesYYYYMMDD. 수정세금계산서 작성일(사유 04 은 이 날짜로 발행) - 그 밖의 사유는 원본 작성일로 발행하고, 이 값은 원본에 발행일이 없을 때 환율조회 기준일로만 쓴다
etxiv_knd_cdNoInvoice kind code. Ignored: the original invoice's kind code is sent ('01' when the original has none). Optional.
account_link_idNoAccount link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure).
etxiv_mdf_rsn_cdYes수정사유코드 - 사용자에게 물어서 받는다. 04 계약의 해제(당초분 전액 음수 1장(계약 해제일)) - 계약 전부가 해제됐을 때만 씁니다(일부 해지는 공급가액 변동). 계약 해제일이 속한 달의 다음 달 10일까지 발급해야 하며, 넘기면 지연발급 가산세 대상입니다. / 06 착오에 의한 이중발급(당초분 전액 음수 1장(당초 작성일)). This is recorded at 국세청 and cannot be undone.
etxiv_dmnr_clsf_cdNoBuyer class code. Ignored: the original invoice's buyer class code is sent ('01' when the original has none). Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / etxiv_dmnr_clsf_cd / description
      Previous value: -"Buyer class code (기본 '01'). Optional."New value: +"Buyer class code. Ignored: the original invoice's buyer class code is sent ('01' when the original has none). Optional."
    • changedInput schema / properties / etxiv_knd_cd / description
      Previous value: -"Invoice kind code (기본 '01'). Optional."New value: +"Invoice kind code. Ignored: the original invoice's kind code is sent ('01' when the original has none). Optional."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare destructiveHint/readOnlyHint; the description goes further by labeling the action IRREVERSIBLE, stating the correction is recorded at 국세청 and cannot be undone, disclosing the per-call token cost (토큰 1소진), and describing the preview-then-confirm requirement. It also explains downstream consequences (deadline and 지연발급 가산세) that no structured field carries.

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 login prerequisite and the status of the operation, and every sentence carries operative information — prereqs, safety, confirm workflow, reason-code sourcing, cost. Dense but justified; the embedded Korean billing note is the only slightly out-of-place element.

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 and 7 parameters, the description covers what an agent needs: prerequisites, the two-step preview/confirm flow, the source of the original approval number, and the irreversibility risk. Nothing essential to a correct call is left unstated.

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 meaning: it tells the agent to solicit etxiv_mdf_rsn_cd from the user and never guess it, and it ties the confirm flag to a user-approval gate. It does not restate the enum semantics beyond routing, so it stops short of a 5.

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 and resource (issue a correcting e-tax invoice, 수정세금계산서) and scopes it as being against an existing invoice, which is what separates it from hometax__etax__invoice__issue. An agent can tell exactly which operation this performs without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit prerequisites (prior hometax__session__login with the same account_link_id), process ('call without confirm first to get a preview, show it to the user, then retry with confirm=true'), and an absolute prohibition ('never guess etxiv_mdf_rsn_cd'). It also names the sibling used to obtain old_aprv_no.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XBOSS toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources