Skip to main content
Glama
seungmiyoon

korean-tax-mcp

by seungmiyoon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

rulings_by_article

Read-onlyIdempotent

Find Korean tax rulings and court precedents that cite a specific statute article, so you can review how that provision is interpreted in practice.

Instructions

List rulings and decisions that cite a specific statute article. 특정 조문을 관련 법령으로 인용한 해석·판례 모음. 언제: 조문을 알고 그 조문의 실무 해석을 모을 때(예: 법인세법 제52조 → 부당행위계산). 키워드만 있으면 search_tax_rulings. 반환: {법령, 조, 결과: [{구분, 문서번호, 제목, 요지, 세목, 일자, id, 링크}]}. 읽기 전용. 국세법령정보시스템 공개 조회(키 불필요), 같은 요청은 1일 캐시.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNo종류별 최대 건수 1~30
taxNo세목 필터 (선택)
langNoOutput language. 'en': English keys and labels, official English texts where available (tax treaties, statutes), titles/summaries machine-translated by Upstage Solar when UPSTAGE_API_KEY is set. 기본 'ko'ko
sortNo정렬최신
kindsNo해석·판례 중 선택. 생략하면 둘 다
articleYes조문 번호. '제52조' 또는 '제28조의2' 형식
keywordNo결과를 좁힐 추가 키워드 (선택)
law_nameYes세법 이름(정식 명칭). 예: '법인세법', '부가가치세법', '소득세법', '상속세 및 증여세법', '국세기본법'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.4.0
    • addedInput schema / properties / article / description
      Added value: +"조문 번호. '제52조' 또는 '제28조의2' 형식"
    • addedInput schema / properties / keyword / description
      Added value: +"결과를 좁힐 추가 키워드 (선택)"
    • changedInput schema / properties / kinds / anyOf
      Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "enum": [
+        "해석",
+        "판례"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / kinds / description
      Added value: +"해석·판례 중 선택. 생략하면 둘 다"
    • addedInput schema / properties / lang
      Added value: +{
+  "default": "ko",
+  "description": "Output language. 'en': English keys and labels, official English texts where available (tax treaties, statutes), titles/summaries machine-translated by Upstage Solar when UPSTAGE_API_KEY is set. 기본 'ko'",
+  "enum": [
+    "ko",
+    "en"
+  ],
+  "title": "Lang",
+  "type": "string"
+}
    • addedInput schema / properties / law_name / description
      Added value: +"세법 이름(정식 명칭). 예: '법인세법', '부가가치세법', '소득세법', '상속세 및 증여세법', '국세기본법'"
    • addedInput schema / properties / n / description
      Added value: +"종류별 최대 건수 1~30"
    • addedInput schema / properties / n / maximum
      Added value: +30
    • addedInput schema / properties / n / minimum
      Added value: +1
    • addedInput schema / properties / sort / description
      Added value: +"정렬"
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "최신",
+  "정확도"
+]
    • changedInput schema / properties / tax / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "법인",
+      "부가",
+      "소득",
+      "양도",
+      "상증",
+      "국기",
+      "국징",
+      "조특",
+      "국조",
+      "종부"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / tax / description
      Added value: +"세목 필터 (선택)"
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/openWorld, but the description adds material context beyond them: it confirms read-only, states no API key is needed (public 국세법령정보시스템 lookup), and discloses a 1-day cache for identical requests. That caching/auth detail is genuinely useful and not derivable from annotations.

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?

Front-loaded with the purpose, then structured into 언제 (when) and 반환 (returns) sections. Efficient and scannable, though the inline return-shape literal is dense and slightly overlaps what the schema could carry.

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?

With no output schema, the description proactively documents the return shape ({법령, 조, 결과:[...]}), plus auth/caching behavior, giving an agent everything needed to call and interpret the tool correctly.

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?

Schema coverage is 100%, so all eight parameters are already documented, including the law_name and article formats and the tax/kinds enums. The description reinforces the law_name+article pairing with an example but adds no syntax or constraints beyond the schema, so the baseline 3 is appropriate.

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?

States a specific verb (List) and resource (rulings/decisions citing a specific statute article), and explicitly distinguishes itself from search_tax_rulings by the input condition. An agent can tell it apart from siblings without opening a schema.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance ('when you know the article and want practical interpretations'), gives a concrete example (법인세법 제52조 → 부당행위계산), and routes the agent to the alternative when only keywords exist. Nothing is left to inference.

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

Deploy Server

Other Tools