Skip to main content
Glama

부가세 사건 생성

vat__case__create

No credential or login required. 한 회사와 신고 기간에 대한 부가세 준비 사건을 생성합니다. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 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": {
      "company_id": "<company_id>",
      "establishment_id": "<establishment_id>"
    },
    "name": "vat__case__create"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNo신규 사건 생성에서 생략하면 한국 날짜 기준 가장 최근 종료된 정기 신고기간을 선택합니다. 최초 회사 등록은 원천과 대조할 기간이 필수이며 기존 사건의 기간은 바뀌지 않습니다.
company_idYes사건을 만들 회사의 ID 입니다. 승인된 회사 프로필에 등록된 회사여야 하고 아니면 거절합니다. 회사 등록(vat.company.register) 때 입력한 company_id 를 그대로 입력합니다.
establishment_idYes사건을 만들 사업장의 ID 입니다. 같은 회사 프로필에 등록된 사업장이어야 하고 아니면 거절합니다. 회사 등록 때 입력한 establishment_id 를 그대로 입력합니다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.
requested_submission_profile_refNo고객이 목적 프로필 참조를 알려 준 경우에만 입력합니다. 새 사건에 쓸 목적 프로필의 참조입니다. 이 회사와 신고 기간에 유효한 승인된 목적 프로필이 없으면 거절합니다. 입력하지 않으면 목적 프로필을 정하지 않고 사건을 만듭니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations it discloses that each call consumes one token, that an XBOSS task is created and the result stored, and that the call is not purely read-only even when the agency source is only queried. That agrees with readOnlyHint=false and destructiveHint=false rather than contradicting them, and adds cost and side-effect detail the annotations cannot express.

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?

Purpose is front-loaded, but the idempotency discussion dominates the text and repeats itself ('Without it, calling again remains a new request'), and the trailing '기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다' is vague filler. Mixed Korean/English also adds noise.

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 mutation tool with full schema coverage and no output schema, the essentials are present: auth need, cost, side effects, idempotency. What is missing is what the returned case contains and what the natural next step is after creation.

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 meaningfully expands request_idempotency_key semantics (recovery-only reuse, new key per execution, and that a provider-specific idempotency_key is a different field). That is real added meaning over the schema's short pointer.

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 Korean sentence '한 회사와 신고 기간에 대한 부가세 준비 사건을 생성합니다' gives a specific verb (생성) and resource (부가세 준비 사건) scoped to a company and filing period. It is clear, though the long idempotency preamble dilutes it and no sibling is contrasted.

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?

The description gives operational guidance for the idempotency key (reuse only to recover a lost response, new key for new execution, anonymous calls cannot use it), which is genuine when-to-use advice. It does not say when to create a case versus using the amendment or draft-load siblings, so routing still requires 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