Skip to main content
Glama

timing_rules

Read-onlyIdempotent

Returns statutory timing rules to determine the business year, tax period, or VAT supply date for tax liability, income receipt, and profit/loss attribution.

Instructions

Timing rules table — tax liability establishment, profit/loss attribution business year, income receipt timing, VAT supply timing, with statutory basis.

시기 규칙표 — 납세의무 성립·손익 귀속사업연도·소득별 수입시기·부가 공급시기를 조문 근거와 함께. 언제: 사실관계의 날짜가 어느 사업연도·과세기간·공급시기에 속하는지 정할 때(예: 12월 인도·1월 대금, 선발급 세금계산서, 인정상여 귀속). 반환: {규칙: [{세목, 구분, 항목, 시기, 예외?(있으면), 근거}], 확인 시행본, 주의, 안내?, 구분 목록?, 기준일 주의?}. tax를 주면 세목 키 포함, tax 없이 부르면 공통 규칙과 세목별 건수. 현행 조문 기준 표(지난 해 규칙 없음). 맞는 규칙이 없거나(0건) 세목 고유 규칙이 없으면(양도·상증·국기·종부) '안내'에 볼 조문을 알려 줌 — law_article로 확인. 읽기 전용. data/timing_rules.json 기반, 외부 호출 없음.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "timing_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxNo세목 필터. '법인'·'소득'·'부가'·'양도'·'상증'·'국기'·'종부' 중 하나(영어 'corporate'·'income'·'VAT'·'capital_gains'·'inheritance_gift'·'basic'·'real_estate'도 받음). 생략하면 공통 규칙과 세목별 건수
kindNo구분 필터(띄어쓰기 무시). 예: '손익 귀속', '재화 공급시기', '용역 공급시기', '공급시기 특례', '근로소득 수입시기', '납세의무 성립'
langNoOutput language. 'en': English keys and labels, official English texts where available (tax treaties, statutes), other Korean texts returned with a host_ai_translate instruction (your AI translates); Solar machine translation only when UPSTAGE_API_KEY or on-prem Solar is configured. 기본 'ko'ko
as_ofNo사안 기준일 YYYYMMDD(선택). 표는 현행 조문만 정리 — 기준일이 표의 확인 시행본보다 앞이면 '기준일 주의'로 알림
keywordNo항목·시기·예외 중 어디에든 포함된 글자 필터 (선택)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.12.10
    • addedInput schema / properties / as_of
      Added value: +{
      +  "default": "",
      +  "description": "사안 기준일 YYYYMMDD(선택). 표는 현행 조문만 정리 — 기준일이 표의 확인 시행본보다 앞이면 '기준일 주의'로 알림",
      +  "title": "As Of",
      +  "type": "string"
      +}
    • changedInput schema / properties / kind / description
      Previous value: -"구분 필터. 예: '손익 귀속', '재화 공급시기', '용역 공급시기', '공급시기 특례', '근로소득 수입시기', '납세의무 성립'"New value: +"구분 필터(띄어쓰기 무시). 예: '손익 귀속', '재화 공급시기', '용역 공급시기', '공급시기 특례', '근로소득 수입시기', '납세의무 성립'"
    • changedInput schema / properties / tax / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "법인",
      -      "부가",
      -      "소득",
      -      "양도",
      -      "상증",
      -      "국기",
      -      "국징",
      -      "조특",
      -      "국조",
      -      "종부"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "법인",
      +      "부가",
      +      "소득",
      +      "양도",
      +      "상증",
      +      "국기",
      +      "국징",
      +      "조특",
      +      "국조",
      +      "종부",
      +      "corporate",
      +      "income",
      +      "VAT",
      +      "capital_gains",
      +      "inheritance_gift",
      +      "basic",
      +      "real_estate"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / tax / description
      Previous value: -"세목 필터. '법인'·'소득'·'부가'·'양도'·'상증'·'국기'·'종부' 중 하나. 생략하면 공통 규칙과 세목별 건수"New value: +"세목 필터. '법인'·'소득'·'부가'·'양도'·'상증'·'국기'·'종부' 중 하나(영어 'corporate'·'income'·'VAT'·'capital_gains'·'inheritance_gift'·'basic'·'real_estate'도 받음). 생략하면 공통 규칙과 세목별 건수"
  2. Addedv0.11.1

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (which already declare read-only, idempotent, non-destructive), the description discloses the return envelope, that only current statutes are tabled with no prior-year rules, the 0-hit fallback that emits an '안내' pointing to articles, the local data source (data/timing_rules.json) and that there are no external calls. The 'no external calls' assertion sits slightly awkwardly against openWorldHint=true, though the safety-relevant hints all agree.

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?

It is dense and well front-loaded with labeled sections (언제 / 반환 / notes), so an agent can scan it quickly. The full bilingual restatement of every line in English doubles the length for limited added value and is the main thing that keeps it from a 5.

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

Completeness5/5

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

For a read-only, five-parameter lookup with no output schema, the description covers purpose, triggers, return shape, scope limits, and the fallback path completely. Nothing an agent needs in order to call it correctly and interpret a zero-result response is missing.

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 already 100%, so the baseline is 3, and the description adds genuine meaning: omitting 'tax' returns common rules plus per-tax counts rather than empty results, 'lang' explains the host_ai_translate fallback versus Solar machine translation, and 'as_of' explains that a date earlier than the tabled edition produces a '기준일 주의' notice. Only 'kind' and 'keyword' semantics are left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (a timing rules table) and enumerates exactly what it covers: tax liability establishment, P/L attribution business year, income receipt timing, and VAT supply timing, each with statutory basis. That enumeration lets an agent distinguish it from generic siblings like basic_rules or execution_standards without opening the schema.

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 has an explicit '언제' section with concrete triggering examples (December delivery / January payment, tax invoice issued in advance, deemed bonus attribution), which is real when-to-use guidance. It also routes the agent onward when nothing matches (0 results, or taxes with no dedicated rules such as 양도·상증·국기·종부) to law_article, but it gives no exclusion versus the other rule-oriented siblings.

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