Skip to main content
Glama

부가세 추천 그룹 조회

vat__recommendation__group__get

자격증명이나 로그인 없이 바로 호출할 수 있습니다. 최종 반영 없이 추천 그룹 하나를 미리 봅니다. 법인 일반과세자가 자기 회사의 부가가치세를 신고할 때 씁니다. 개인사업자, 간이과세자 신고와 세무대리인 신고는 아직 지원하지 않습니다. 로그인한 호출이면 첫 요청 전에 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": {
      "case_id": "<case_id>",
      "explain_domain": "<explain_domain>",
      "explain_group_index": "<explain_group_index>"
    },
    "name": "vat__recommendation__group__get"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYes추천 묶음을 조회할 부가세 준비 사건의 ID 입니다. 사건 생성(vat.case.create) 결과의 case_id 를 그대로 입력합니다.
explain_domainYes조회할 추천의 영역입니다. PURCHASE(매입) 또는 SALES(매출)입니다.
explain_group_indexYes조회할 추천 묶음의 순번입니다. 0 부터 세는 정수이고 묶음 수(group_count) 이상이면 거절합니다.
explain_snapshot_refNo이전에 받은 단계 결과의 snapshot_ref 입니다. 입력하면 단계 결과가 그때와 같을 때만 돌려주고 사건이 다시 분석되어 달라졌으면 거절합니다. 입력하지 않으면 지금 결과를 돌려줍니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already flag readOnlyHint=false, and the description reinforces this with an explicit warning that the call is not purely read-only even though the institutional original is a lookup. Beyond that, it discloses token cost per call, the creation of an XBOSS task with stored results, and the credential-free (or optional-login) access model. It also fully explains the idempotency-key retrieval protocol, including that reuse without a 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.

Conciseness3/5

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

The content is valuable, but it is delivered as an unstructured wall of sentences, opening with credential handling rather than the tool's purpose. The idempotency and XBOSS-task material could be tightened, and several clauses restate the same point about read-only versus side effects.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Auth model, eligibility, cost, side effects, and idempotency are all well covered, which is strong for a five-parameter tool. However, there is no output schema and the description never indicates what a 'recommendation group' contains or what a preview response looks like, leaving the agent unable to anticipate the return value or the logical next step.

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 goes further: the request_idempotency_key field's schema explicitly defers to the description ('쓰는 법은 도구 설명에 있습니다'), and the description fills that in with generate-before-first-request, reuse-only-for-recovery, and unavailability on unauthenticated trial calls. It also clarifies that the institutional idempotency_key is a distinct field not to be confused with this one.

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?

The description states a concrete action and resource: previewing a single recommendation group ('최종 반영 없이 추천 그룹 하나를 미리 봅니다'), and it pins the supported filer type (corporate general taxpayer filing its own VAT). It stops short of explicitly differentiating itself from nearby lookup tools such as vat__analysis__snapshot__get, so an agent must infer the boundary from the parameters.

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?

It gives explicit eligibility conditions and clear exclusions ('개인사업자, 간이과세자 신고와 세무대리인 신고는 아직 지원하지 않습니다'), which is real when-to-use guidance. It never names an alternative tool to use when those exclusions apply, so the routing decision is left partly 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