Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

사업자등록증 재발급 신청

hometax__certificate__apply__business_registration_reissue
Destructive

REQUIRES prior hometax__session__login call with same account_link_id. Apply for Business Registration Reissuance. IRREVERSIBLE: this files an application with the NTS and a receipt record (cvaId + rcatNo) is created; there is no cancel action. Call without confirm first to get a preview, show it to the user, then retry with confirm=true. Never set confirm=true on your own. 호출마다 토큰 1소진

Input Schema

NameRequiredDescriptionDefault
adrOpYnNo주소 표시 여부(Y/N) (서식의 선택 입력)
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.
resnoOpYnNo주민등록번호 표시 여부(Y/N, 법인은 N 고정) (서식의 선택 입력)
cerpIsnRqsQtyNo발급 매수 (서식의 선택 입력)
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).
cvaDcumGranMthdCdNo교부방법 코드 (서식의 선택 입력)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / adrOpYn / description
      Previous value: -"Show address on the certificate: 'Y' or 'N'"New value: +"주소 표시 여부(Y/N) (서식의 선택 입력)"
    • removedInput schema / properties / amtOpYn
      Removed value: -{
-  "description": "Show amount: 'Y' or 'N'",
-  "type": "string"
-}
    • changedInput schema / properties / cerpIsnRqsQty / description
      Previous value: -"Number of copies to issue (발급 매수)"New value: +"발급 매수 (서식의 선택 입력)"
    • changedInput schema / properties / cvaDcumGranMthdCd / description
      Previous value: -"Delivery method code (교부방법 코드)"New value: +"교부방법 코드 (서식의 선택 입력)"
    • removedInput schema / properties / cvaDcumSbmsOrgnClCd
      Removed value: -{
-  "description": "Submission target code (제출처 구분코드)",
-  "type": "string"
-}
    • changedInput schema / properties / resnoOpYn / description
      Previous value: -"Show resident number: 'Y' or 'N' (forced 'N' for corporations)"New value: +"주민등록번호 표시 여부(Y/N, 법인은 N 고정) (서식의 선택 입력)"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial context beyond the destructiveHint=true annotation: the application is filed with the NTS, a receipt record with cvaId and rcatNo is created, and there is no cancel action. It also discloses a per-call token cost and the auth dependency, which the annotations do not convey.

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?

Five short sentences, front-loaded with the prerequisite and the irreversibility warning before the procedural detail. Every sentence carries a distinct obligation: auth, effect, reversibility, confirmation flow, cost.

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?

For a no-required-param, no-output-schema mutation tool, the description covers everything an agent needs: prerequisite login, destructive and non-reversible nature, the preview/confirm protocol, and the returned receipt identifiers. Nothing material is missing.

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 all six parameters are already documented in the schema, including the confirm flag's preview semantics. The description reinforces the confirm workflow but adds no new meaning about the Korean form fields (adrOpYn, resnoOpYn, cerpIsnRqsQty, cvaDcumGranMthdCd), so the baseline of 3 applies.

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: 'Apply for Business Registration Reissuance,' which is clearly narrower than the sibling hometax__certificate__apply__business_registration. It does not explicitly contrast with apply_auto or apply_with_template, so sibling differentiation relies on the name rather than the prose.

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?

Gives an explicit prerequisite (prior hometax__session__login with the same account_link_id) and a precise two-step workflow: call without confirm for a preview, show the user, then retry with confirm=true. It adds a hard prohibition ('Never set confirm=true on your own') but never names when a different sibling apply tool would be the correct choice.

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