Skip to main content
Glama
seungmiyoon

korean-tax-mcp

by seungmiyoon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

casebook_search

Read-onlyIdempotent

Search the Korean NTS 2025 Tax Interpretation Casebook to retrieve 96 curated representative tax interpretation cases for offline reference.

Instructions

Search the NTS 2025 Tax Interpretation Casebook (96 curated cases). 국세청 「2025 세법해석 사례집」 쟁점 검색. 언제: 국세청이 대표 사례로 고른 해석을 빠르게 볼 때(오프라인, 즉시). 최신·전체 해석은 search_tax_rulings. 반환: {결과: [{문서번호, 회신일, 분야, 쟁점, 답변요지, 쪽, 점수, 인용}]}. 읽기 전용, 외부 호출 없음.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNo결과 수 1~10
areaNo분야 필터 (선택)
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
queryYes쟁점 문장이나 키워드

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.4.0
    • changedInput schema / properties / area / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "법인",
+      "부가",
+      "소득",
+      "상증",
+      "양도",
+      "국기",
+      "국조",
+      "종부"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / area / description
      Added value: +"분야 필터 (선택)"
    • addedInput schema / properties / k / description
      Added value: +"결과 수 1~10"
    • addedInput schema / properties / k / maximum
      Added value: +10
    • addedInput schema / properties / k / minimum
      Added value: +1
    • 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 / query / description
      Added value: +"쟁점 문장이나 키워드"
  2. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, and the description partly repeats that ('읽기 전용, 외부 호출 없음'). However it adds genuinely new traits: the 'offline, instant' latency profile and, since no output schema exists, an explicit return shape showing each result carries score and citation. The repetition of annotation content 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.

Conciseness5/5

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

Front-loaded with the core purpose, then cleanly labeled sections for when ('언제') and return ('반환'). Every sentence carries distinct information with no padding.

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?

Covers purpose, scope (96 cases), when-to-use, the competing sibling, and the return structure despite there being no output schema. Combined with annotations that fully cover the safety profile, an agent has everything needed to call it 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 description coverage is 100%, so the schema already documents query, k, area, and lang (including the lang behavior and the enum values). The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 and resource (search the NTS 2025 Tax Interpretation Casebook) and scopes it precisely with '96 curated cases.' It also names the sibling search_tax_rulings so the agent can distinguish this curated/offline corpus from the full/latest rulings search without opening either 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?

The '언제' clause gives an explicit when: quickly viewing NTS-selected representative interpretations (offline, instant). It also names the alternative ('최신·전체 해석은 search_tax_rulings') with the condition that selects it, leaving nothing 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