Skip to main content
Glama
seungmiyoon

korean-tax-mcp

by seungmiyoon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_tax_ruling

Read-onlyIdempotent

Fetch the full text of a single Korean tax ruling or court decision by ID to read facts, issues, and holdings before citing or summarizing search results.

Instructions

Get the full text of one ruling or decision. 해석·판례 1건의 본문 전문. 언제: 검색 결과 중 인용·요약할 문서를 정한 뒤. 요지만으로 판단하지 말고 본문을 읽을 때 사용. 반환: {문서번호, 제목, 요지, 등록일, 관련조문[], 본문(질의회신: 사실관계·질의·회신 / 판례: 주문·이유, 최대 2만 자), 링크}. 읽기 전용. 국세법령정보시스템 공개 조회(키 불필요), 같은 요청은 1일 캐시.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYessearch_tax_rulings·rulings_by_article 결과의 id (숫자 12~20자리)
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • addedInput schema / properties / id / description
      Added value: +"search_tax_rulings·rulings_by_article 결과의 id (숫자 12~20자리)"
    • 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"
+}
  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, openWorldHint, and destructiveHint=false. The description adds useful context beyond annotations: it states no API key is needed, that it uses the public 국세법령정보시스템, and that responses are cached for 1 day. This is solid additional behavioral detail, though return format is partially covered by the '반환' note (which is helpful since there's no output schema).

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?

Very well-structured with front-loaded purpose, followed by clear sections for when to use (언제) and what is returned (반환), plus a brief note on behavior. Every sentence is informative and earns its 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?

Given the tool's simplicity (2 parameters, no output schema), the description is quite complete. It covers purpose, usage, return structure, and operational context. Minor gap: the '반환' section describes fields but not their exact data types or edge cases (e.g., missing fields), which could be helpful without an output schema.

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 both parameters, including the id's origin and format, and the lang enum's behavior. The description does not add parameter-level detail beyond what the schema provides. 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 (Get) and resource (full text of one ruling or decision), and clearly scopes it to retrieving a single document's body. It is easily distinguishable from sibling search/list tools like search_tax_rulings and rulings_by_article.

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?

Explicitly states when to use it ('after selecting a document from search results to cite or summarize') and includes a caveat ('don't judge based only on the summary – use this to read the full text'). This gives clear direction versus alternatives.

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