Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

납부 내역 조회

hometax__tax__payment_statement__search
Read-only

REQUIRES prior hometax__session__login call with same account_link_id. Search tax payment statement. mate_knd_cd: document type code. sbms_ym_strt/sbms_ym_end: submission year-month YYYYMM. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 1소진

Input Schema

NameRequiredDescriptionDefault
page_numNoPage number (default 1)
page_sizeNoPage size (default 10)
mate_knd_cdYesDocument type code (자료종류코드) — one of: A0051 근로소득 지급명세서 / A0053 퇴직소득 지급명세서 / A0056 의료비 명세서 / A0057 기부금 명세서 / A0086 사업소득 지급명세서 / A0085 사업소득(연말정산용) 지급명세서 / A0088 기타소득 지급명세서 / A0087 종교인소득(연말정산용) 지급명세서 / A0084 이자·배당소득 지급명세서 / A0283 연금계좌 지급명세서 / A0055 비거주자 사업·기타소득 지급명세서 / A0259 부동산등 양도소득 지급명세서 / A0257 유가증권 양도소득 지급명세서. Any other value is refused before the NTS is contacted.
sbms_ym_endYesSubmission end year-month YYYYMM
sbms_ym_strtYesSubmission start year-month YYYYMM
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).
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request_idempotency_key
      Added value: +{
+  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7E]+$",
+  "type": "string"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them. Beyond that it discloses the auth dependency, idempotency-key lifecycle semantics (reuse only to recover a lost response, new key for a new execution), the existence of a distinct provider idempotency_key field, and a per-call token cost — real behavioral context the annotations do not 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 is correctly front-loaded, but roughly half the text is generic idempotency boilerplate aimed at one optional parameter, including the awkward phrase 'anonymous taste calls'. Signal-to-noise is mediocre even though no single sentence is meaningless.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the auth chain, parameters, and cost, but with no output schema the description never says what a payment statement result contains, and it ignores the page_num/page_size pagination behavior entirely. Adequate to invoke, incomplete for interpreting results.

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 lifts it slightly by defining the semantics of request_idempotency_key, which the schema explicitly defers to the description ('see the tool description'). The mate_knd_cd and sbms_ym restatements are largely redundant with the enum-rich 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?

States a specific verb and resource ('Search tax payment statement') in a single clear sentence, and the title matches. It does not distinguish itself from the close sibling hometax__tax__payment_statement__search_submit_history, so an agent must infer the boundary between the two.

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 ('REQUIRES prior hometax__session__login call with same account_link_id') and detailed when-to-reuse guidance for the idempotency key. It lacks any statement of when to prefer a sibling search tool, but the precondition guidance is strong.

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