XBOSS

부가세 분석 실행

vat__analysis__run

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": {
      "case_id": "<case_id>",
      "expected_revision": "<expected_revision>"
    },
    "name": "vat__analysis__run"
  }
}

Input Schema

Name	Required	Description
`case_id`	Yes	분석할 부가세 준비 사건의 ID 입니다. 사건 생성(vat.case.create) 결과의 case_id 를 그대로 입력합니다.
`analysis_scope`	No	분석을 어느 단계까지 실행할지 정하는 객체입니다. stop_after_stage 에 V01 부터 V12 가운데 하나를 입력하고, 입력하지 않으면 마지막 단계까지 실행합니다.
`expected_revision`	Yes	사건의 지금 revision 입니다. 직전 작업 결과의 case_revision 을 그대로 입력합니다(새로 만든 사건은 1). 그 사이 사건이 바뀌었으면 거절하므로 사건을 다시 조회한 뒤 요청합니다.
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.
`requested_submission_profile_ref`	No	고객이 목적 프로필 참조를 알려 준 경우에만 입력합니다. 이 사건에 쓸 목적 프로필의 참조입니다. 등록되어 승인된 목적 프로필이어야 하고 아니면 거절합니다. 입력하지 않으면 사건의 목적 프로필을 바꾸지 않습니다.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

B3.4/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds real context beyond them: each call consumes one token ('호출마다 토큰 1소진'), the call creates an XBOSS job and stores results, and it explicitly warns that the call is not purely read-only even when the source agency data is only queried. That is consistent with the annotations and useful for an agent weighing side effects. It does not describe failure modes or latency, so it is not 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.

Conciseness2/5

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

The description is long, mixes Korean and English, and repeats the idempotency-key rules across several sentences ('Reuse it with the same arguments only to recover that request...', 'Without it, calling again remains a new request', 'This optional key is not available to anonymous taste calls'). The purpose statement is buried after a credential sentence, and the closing sentences about agency data changes are vague filler. Several sentences do not earn their place.

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 five-parameter, non-read-only pipeline tool with no output schema, the description covers the important behavioral facts: cost per call, job creation and result storage, idempotency semantics, and the non-read-only nature. Revision-conflict behavior is handled in the schema. It is close to complete, though it omits what the analysis returns and how long a run takes.

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. The description goes beyond the schema for request_idempotency_key, whose schema entry only says 'see the tool description': it explains when to generate the key, when to reuse it, when to use a new one, and that it is unavailable to anonymous calls. That is genuine added meaning. The other parameters are left to the schema, which is acceptable given full coverage.

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 specific verb and resource: '표준 부가세 준비 분석 파이프라인을 실행합니다' (runs the standard VAT preparation analysis pipeline). That is clear enough for an agent to know what the tool does. However, it never distinguishes this tool from siblings such as vat__case__create or vat__card__review__import_and_apply, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool instead of alternatives, and no prerequisites or exclusions. The only usage-like content concerns the idempotency key mechanics ('generate and save request_idempotency_key before the first request'), which is parameter handling rather than tool selection. An agent must infer the tool's place in the workflow from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XBOSS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?