Skip to main content
Glama

신용카드 매출자료 조회

hometax__tax__credit_card__search_sales_data

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 신용카드 매출자료를 조회합니다. bsno 는 사업자등록번호, stl_yr 는 연도(YYYY), qrt_from/qrt_to 는 분기(1부터 4)입니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 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": {
      "bsno": "<bsno>",
      "stl_yr": "<stl_yr>",
      "qrt_from": "<qrt_from>",
      "qrt_to": "<qrt_to>"
    },
    "name": "hometax__tax__credit_card__search_sales_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
bsnoYes사업자등록번호.
qrt_toYes종료 분기. '1' 부터 '4' 가운데 하나입니다.
stl_yrYes연도 YYYY (예: '2026').
page_numNo쪽 번호. 기본 1.
qrt_fromYes시작 분기. '1' 부터 '4' 가운데 하나입니다.
page_sizeNo한 쪽에 받을 건수. 기본 50.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / bsno / description
      Previous value: -"Business registration number"New value: +"사업자등록번호."
    • changedInput schema / properties / page_num / description
      Previous value: -"Page number (default 1)"New value: +"쪽 번호. 기본 1."
    • changedInput schema / properties / page_size / description
      Previous value: -"Page size (default 50)"New value: +"한 쪽에 받을 건수. 기본 50."
    • changedInput schema / properties / qrt_from / description
      Previous value: -"Start quarter '1'~'4'"New value: +"시작 분기. '1' 부터 '4' 가운데 하나입니다."
    • changedInput schema / properties / qrt_to / description
      Previous value: -"End quarter '1'~'4'"New value: +"종료 분기. '1' 부터 '4' 가운데 하나입니다."
    • changedInput schema / properties / stl_yr / description
      Previous value: -"Settlement year YYYY (e.g. '2026')"New value: +"연도 YYYY (예: '2026')."
  2. Changed1 schema field changed
    • changedInput schema / properties / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses a per-call cost ("호출마다 토큰 1소진"), that a call creates and stores an XBOSS job, and explicitly warns that despite being a lookup this call is not purely read-only — consistent with readOnlyHint=false. It also explains that the agency's own idempotency_key field is a different parameter and must be left alone.

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?

Front-loads the prerequisite, then purpose, then parameters, which is a sensible order. However, the idempotency paragraph is four to five sentences with internal restatement ("이 값 없이 다시 부르면 새 요청이 됩니다"), and the closing sentences about XBOSS and agency data-change procedures are diffuse boilerplate.

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 8 parameters, full schema coverage, and no output schema, the description covers prerequisites, parameter meanings, retry semantics, cost, and side effects. It never hints at the shape of the returned sales records (fields, per-page totals), which would matter given the absence of an output schema, and non-Korean ids in the schema (page_num/page_size) go unmentioned.

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 on top: it restates bsno/stl_yr/qrt_from/qrt_to semantics compactly and, crucially, supplies the usage rules for request_idempotency_key that the schema itself defers to the description. That makes the otherwise opaque idempotency parameter actionable.

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: "신용카드 매출자료를 조회합니다" (retrieve credit card sales data), which tells an agent exactly what is fetched. It does not distinguish itself from related siblings such as hometax__cash_receipt__sales__search_history or the kb_biz_card approval/purchase tools, so the agent must infer the boundary.

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 a concrete prerequisite ("먼저 호출할 도구: hometax__session__login (같은 account_link_id)") and precise retry guidance for the idempotency key: reuse it only to recover a request whose response was lost, otherwise use a new value. It also states that the optional key cannot be used in no-account trial mode. Missing is guidance on when to choose this tool over sibling sales/invoice lookups.

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