Skip to main content
Glama

현금영수증 매출 합계 조회

hometax__cash_receipt__sales__search_summary

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 현금영수증 매출의 연간 합계를 조회합니다. cmtt_yr 에 대상 연도를 넣고, 분기별로 보려면 qrt(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": {
      "cmtt_yr": "<cmtt_yr>"
    },
    "name": "hometax__cash_receipt__sales__search_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrtNo분기. 1 부터 4 가운데 하나입니다. 입력하지 않으면 연간 합계를 조회합니다.
cmtt_yrYes대상 연도 YYYY (예: '2025'). 필수입니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / cmtt_yr / description
      Previous value: -"Target year YYYY (e.g. '2025'). Required."New value: +"대상 연도 YYYY (예: '2025'). 필수입니다."
    • changedInput schema / properties / qrt / description
      Previous value: -"Quarter 1-4. Optional — omit for full-year summary."New value: +"분기. 1 부터 4 가운데 하나입니다. 입력하지 않으면 연간 합계를 조회합니다."
  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

A3.9/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: one token consumed per call, an XBOSS job created and its result stored, and an explicit warning that the call is not purely read-only despite being a lookup. This is consistent with readOnlyHint=false. The idempotency-key retry semantics are also spelled out, though the wording is dense.

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 prerequisite is correctly front-loaded, but the body mixes idempotency instructions, token cost, and XBOSS job behavior into a long run of sentences with some redundancy (e.g., restating that calling without the key creates a new request). It is informative but not tight.

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 no output schema, the description carries the burden of describing returns, and it does state that the result is an annual total with optional quarterly breakdown. Combined with the auth prerequisite and idempotency rules, an agent has enough to invoke it correctly.

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: cmtt_yr is the target year, qrt selects quarterly granularity, request_idempotency_key is only for retrying an unanswered request, and account_link_id is unavailable in unauthenticated trial mode. It also warns not to confuse the field with the institution's own idempotency_key.

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 ('현금영수증 매출의 연간 합계를 조회합니다') and names the required prerequisite tool. It does not explicitly contrast with the sibling search_history tool, so an agent must infer that this returns aggregates rather than line items.

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 clear operational context: call hometax__session__login first with the same account_link_id, put the year in cmtt_yr, and add qrt (1-4) only for quarterly views. It lacks explicit when-not-to-use guidance versus the history/detail siblings.

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