Skip to main content
Glama

사업자등록 상태 조회

hometax__tax__business_registration__search_status

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 사업자등록번호로 사업자등록 상태를 조회합니다. 로그인한 호출이면 첫 요청 전에 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": {
      "txpr_dscm_no": "<txpr_dscm_no>"
    },
    "name": "hometax__tax__business_registration__search_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
txpr_dscm_noYes사업자등록번호(숫자 10자리, 하이픈은 자동으로 뺍니다. 예: '1234567890' 또는 '123-45-67890').
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 / txpr_dscm_no / description
      Previous value: -"Business registration number 사업자등록번호 (10 digits, hyphens stripped automatically, e.g. '1234567890' or '123-45-67890')."New value: +"사업자등록번호(숫자 10자리, 하이픈은 자동으로 뺍니다. 예: '1234567890' 또는 '123-45-67890')."
  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.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that despite being a lookup this call is not purely read-only — it creates an XBOSS task and stores processing results — which explains the readOnlyHint=false annotation. It also discloses a per-call cost of 1 token and the full idempotency/retry protocol, including that a call without the key counts as a new request.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the prerequisite tool, then the purpose, then the key protocol and cost/side-effect notes, so the most important facts come first. The closing sentence about institution data changes being 'per tool execution content and existing confirmation procedures' is vague boilerplate that adds little.

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?

For a 3-parameter tool with annotations and no output schema, it covers prerequisites, cost, side effects, and parameter protocol thoroughly. The main remaining gap is that it never describes what the lookup returns (e.g., the possible status values), which an agent calling a status-check tool would want.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the schema's request_idempotency_key entry defers its usage rules to the description, and the description delivers them: generate and store a value before the first request, reuse it only to recover an unanswered request, use a fresh value for new executions. It also warns that the institution's separate idempotency_key field is a different field and should be left untouched, preventing a likely mix-up.

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: lookup business registration status by business registration number (사업자등록번호로 사업자등록 상태를 조회합니다), and leads with the prerequisite login tool. It does not, however, distinguish itself from the close sibling hometax__tax__business_registration__search_info, so an agent must still infer which of the two business-registration lookups to pick.

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?

Explicitly names the tool to call first (hometax__session__login with the same account_link_id) and explains when the idempotency key may be used (logged-in calls, retry of an unanswered request) and when it may not (unauthenticated 'taste' calls). It gives no exclusion criteria relative to sibling lookup tools, so it stops short of full when/when-not guidance.

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