Skip to main content
Glama

전자세금계산서 상세 조회

hometax__etax__invoice__search_detail

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 승인번호(etan)로 전자세금계산서 한 건의 상세 정보를 조회합니다. etan 은 hometax__etax__invoice__search_list 결과에서 얻습니다. 로그인한 호출이면 첫 요청 전에 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": {
      "etan": "<etan>"
    },
    "name": "hometax__etax__invoice__search_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
etanYes승인번호(24자). hometax__etax__invoice__search_list 결과에서 가져옵니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / etan / description
      Previous value: -"Invoice approval number (승인번호, 24 chars). Obtain from hometax__etax__invoice__search_list results."New value: +"승인번호(24자). hometax__etax__invoice__search_list 결과에서 가져옵니다."
  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.6/5.0
Behavior5/5

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

Beyond the annotations it discloses per-call token cost ('호출마다 토큰 1소진'), a real side effect ('요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다'), and the important warning that the call is not purely read-only despite being a lookup. This is consistent with readOnlyHint=false and adds information the annotations cannot convey.

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 content is useful but densely packed into a single block, and the prerequisite ('먼저 호출할 도구') is front-loaded ahead of the purpose statement, delaying what the tool actually does. Several operational concerns (idempotency, token cost, XBOSS task, no-account trial) are concatenated without structure, making the key warning about non-read-only behavior easy to miss.

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?

Given no output schema, the description covers prerequisites, identity keys, cost, side effects, and idempotency thoroughly; the notable gap is that it never indicates what the returned invoice detail contains, which matters for a detail-lookup tool. The remaining elements an agent needs to call it correctly are present.

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 schema already defines all three parameters, but the description adds operational meaning: the recovery-only resend semantics of request_idempotency_key, the warning that resending without it creates a new request, and the caution not to confuse it with the institution-side idempotency_key field. That is more than naming fields, though account_link_id scoping is only implied ('같은 account_link_id').

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?

The description states a specific verb and resource ('승인번호(etan)로 전자세금계산서 한 건의 상세 정보를 조회합니다') and pins the scope to a single record keyed by approval number. It also distinguishes itself from the sibling list tool by naming where the etan comes from (search_list), so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives the prerequisite ('먼저 호출할 도구: hometax__session__login (같은 account_link_id)'), how to obtain the required etan from search_list, and an explicit exclusion ('계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다'). When-to-reuse versus when-to-generate-fresh idempotency keys is spelled out rather than left to inference.

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