Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

일일 현금영수증 취소

hometax__cash_receipt__daily_issue__cancel
Destructive

REQUIRES prior hometax__session__login call with same account_link_id. Cancel a cash receipt issued today. Only aprv_no and cshpt_cncl_rsn_cd are needed: every other field is taken from today's original receipt when omitted (get aprv_no from hometax__cash_receipt__daily_issue__search). 호출마다 토큰 1소진

Input Schema

NameRequiredDescriptionDefault
tipNoService charge (봉사료). Taken from today's original receipt when omitted.
trs_dtNoTransaction date YYYYMMDD. Default: the original receipt's date (only today's receipts can be cancelled).
aprv_noYesApproval number (승인번호)
confirmNoSet true ONLY after showing the preview to the user and receiving their explicit approval. Omit it on the first call to obtain the preview.
spl_cftNoSupply value (공급가액). Taken from today's original receipt when omitted.
rcpr_tinNoRecipient TIN. Taken from today's original receipt when omitted.
trs_timeNoTransaction time HHMMSS. Taken from today's original receipt when omitted.
va_txamtNoVAT amount (부가세). Taken from today's original receipt when omitted.
tota_trs_amtNoTotal transaction amount (총 거래금액, KRW as string, minimum 1) Taken from today's original receipt when omitted.
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).
cshpt_usg_cl_cdNoUsage class code (용도구분코드): 0=소득공제용, 1=지출증빙용 Taken from today's original receipt when omitted.
spst_cnfr_cl_cdNoIssue-means class code (발급수단구분코드): 01=주민등록번호, 02=사업자등록번호, 03=휴대전화번호, 04=카드번호 Taken from today's original receipt when omitted.
cshpt_cncl_rsn_cdYesCancel reason code (1=거래취소, 2=오류발급, 3=기타)
cshpt_trs_type_cdNoTransaction type code (거래유형코드): 01=과세, 02=면세, 03=간이 Taken from today's original receipt when omitted.
spst_cnfr_no_enc_cntnNoIssue-means number (발급수단번호) matching the class code, digits only. It is sent to the institution exactly as given - never encrypt or hash it, and never put an approval number here. Taken from today's original receipt when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds behavior beyond that: session-auth dependency, the today-only restriction that bounds what can be destroyed, the token-per-call quota cost, and the fact that omitted fields are re-derived from the original receipt. That is genuine operational context, not restatement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with the login prerequisite and then the minimal-call recipe. No filler; even the token-cost note is a single compact clause.

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 15-parameter destructive tool with no output schema, the essentials (auth, scope, minimal inputs, cost) are covered. The notable omission is the two-step preview/confirm workflow, which is only documented inside the confirm parameter's schema description rather than in the description itself.

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; the description adds value by telling the agent a minimal call needs only aprv_no and cshpt_cncl_rsn_cd and where aprv_no comes from. It doesn't explain the confirm/preview step or the enum meaning of the reason code, leaving part of the semantics to the schema.

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?

A specific verb+resource+scope: 'Cancel a cash receipt issued today.' It also distinguishes itself from the sibling lookup tool by naming search as the source of aprv_no, so an agent can pick between issuing, searching, and cancelling without opening schemas.

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?

States the hard prerequisite (prior session__login with the same account_link_id), the eligibility constraint (today's receipts only), where to obtain aprv_no, and the per-call token cost. It doesn't contrast against the closely related daily_issue__modify tool, which leaves one sibling ambiguity unresolved.

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