Skip to main content
Glama

사업자 정보 조회 (전자세금계산서)

hometax__etax__business_info__get

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 전자세금계산서 발행에 쓰는 사업자 정보를 조회합니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hometax__etax__business_info__get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds real behavior: a per-call token cost, creation of an XBOSS job that stores a processing result, and an explicit warning that the call is not purely read-only regardless of whether the agency source is queried. That is genuine disclosure beyond the annotations, consistent with readOnlyHint=false. The trailing sentence about '기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다' is vague boilerplate with little informational value.

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 and the idempotency rules earn their place, but the ordering is awkward (prerequisite before purpose) and the closing sentence about agency data changes is filler. Several idempotency sentences could be compressed into one or two without losing meaning.

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?

Critical operational facts — auth prerequisite, cost, side effects, retry contract — are all present for a two-optional-parameter tool. With no output schema, the description would ideally enumerate what business fields come back (registration number, name, representative), which it does not. That is the main remaining gap.

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 both parameters are already described, and the schema explicitly defers idempotency usage to the tool description. The description delivers that: when to mint the key, when to resend it vs. mint a new one, unauthenticated-mode exclusion, and a warning not to confuse it with the agency-side idempotency_key field. account_link_id semantics are only touched via the login prerequisite.

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 ('전자세금계산서 발행에 쓰는 사업자 정보를 조회합니다'), scoping it to e-tax-invoice issuance. An agent can tell it apart from write siblings like invoice__issue. It does not, however, distinguish itself from close look-alikes such as etax__client_info__get or tax__business_registration__search_info.

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 ('먼저 호출할 도구: hometax__session__login (같은 account_link_id)') including the required matching argument, plus a clear when-not for the optional field in unauthenticated trial calls. Retry-vs-new-request semantics for the idempotency key are spelled out. It stops short of saying when to prefer this over the other business-info 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