Skip to main content
Glama

부가세 사건 조회

vat__case__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>"
    },
    "name": "vat__case__get"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYes
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. Added

TDQS

A3.5/5.0
Behavior4/5

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

Substantial context beyond the annotations: it discloses that no login is required, that each call consumes one token, that a request creates an XBOSS task and stores a result, and explicitly warns the call is not pure read-only even though it is a 'get'. This is consistent with readOnlyHint=false and adds real value. The closing line about institutional data changes following 'each tool's execution content and existing confirmation procedures' is vague, which keeps it from a 5.

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 largely substantive (idempotency rules, token cost, side effects) rather than filler, but the ordering is poor: credential notes precede the actual purpose, and the read-only disclaimer arrives last. It reads as accumulated caveats rather than a front-loaded explanation.

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?

For a two-parameter tool with no output schema, the side-effect and cost disclosures are helpful, but the description never indicates what 'preparation status' actually returns or what case_id refers to. An agent knows how to call it safely yet not what it will get back or what identifier to supply.

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

Parameters3/5

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

With 50% schema coverage, the description compensates well for request_idempotency_key by explaining exactly when to reuse versus regenerate it, and it clarifies that the separate institutional idempotency_key field is different and should be left alone. But case_id, the sole required parameter, is undocumented in both schema and description, leaving its semantics unexplained.

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 second sentence states a specific verb and resource: it looks up the current VAT case and its preparation status. That is clear enough to distinguish it from vat__case__create, though the core purpose is buried behind an opening sentence about credentials rather than front-loaded.

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

Usage Guidelines3/5

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

It gives useful conditional guidance about the idempotency key (new value for a new run, same value only to recover an unanswered request) and notes that unauthenticated 'taste test' calls cannot use that field. However, it never says when to reach for this tool versus a sibling like vat__case__create or the analysis tools, so routing guidance is only implied by the name.

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