Skip to main content
Glama
seungmiyoon

korean-tax-mcp

by seungmiyoon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

execution_standards

Read-onlyIdempotent

Find Korean tax enforcement standards by law, article, or keyword and get item titles with page numbers. Read-only public lookup, no API key needed.

Instructions

List Tax Execution Standards (세법집행기준) items with page numbers. 세법집행기준 항목(최신 발간본). 언제: 조문별 집행 기준이 있는지·몇 쪽인지 확인할 때. 본문은 책자(PDF)라 제공하지 않으므로 통칙 본문이 필요하면 basic_rules. 반환: {법령, 기준(발간 연도), 항목: [{항목(번호·제목), 쪽}], 링크, 주의}. 읽기 전용. 국세법령정보시스템 공개 조회(키 불필요), 같은 요청은 1일 캐시.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
articleNo법 조문('제52조'). 주면 그 조의 집행기준 항목만
keywordNo항목 제목 검색어 (선택)
law_nameYes세법 이름(정식 명칭). 예: '법인세법', '부가가치세법', '소득세법', '상속세 및 증여세법', '국세기본법'. 소득세는 '소득세법'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.0
    • addedInput schema / properties / article / description
      Added value: +"법 조문('제52조'). 주면 그 조의 집행기준 항목만"
    • addedInput schema / properties / keyword / 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: +"세법 이름(정식 명칭). 예: '법인세법', '부가가치세법', '소득세법', '상속세 및 증여세법', '국세기본법'. 소득세는 '소득세법'"
  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 declare readOnlyHint, idempotentHint and destructiveHint=false, so the trailing 읽기 전용 is largely redundant. The description does add genuinely new operational context beyond annotations: no API key required for the public NTS lookup and a one-day cache for identical requests.

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-loads the one-line purpose, then uses labeled 언제/반환/operational blocks that each carry distinct information. Dense but waste-free; only the 읽기 전용 phrase overlaps structured annotations.

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?

Despite having no output schema, the description fully specifies the return shape ({법령, 기준, 항목:[{항목, 쪽}], 링크, 주의}), plus the critical limitation that content is PDF-only. Nothing an agent needs to call or interpret this tool is missing.

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 law_name, article, keyword and lang are all documented in the schema itself; baseline 3 applies. The description's mention of '조문별' loosely echoes the article filter but adds no syntax, format or default guidance beyond what the schema already supplies.

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 ('List Tax Execution Standards items with page numbers') and pins the scope to the latest published edition. It explicitly distinguishes itself from the sibling basic_rules for body text, so an agent can route correctly 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 '언제' line gives the exact triggering condition (checking whether an article-level standard exists and on which page), and it adds an explicit exclusion plus alternative: body text is not provided here, so use basic_rules when the 통칙 body is needed. This is textbook when/when-not/alternative guidance.

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