Skip to main content
Glama

tax_treaty

Read-onlyIdempotent

Look up articles of Korea’s bilateral tax treaties by country and keyword to check withholding tax limits, permanent establishment, and residency rules in Korean or English.

Instructions

Read Korea's bilateral tax treaties (96 countries) article by article, Korean or English. 한국의 조세조약 조문(국문·영문). 언제: 비거주자 원천징수 제한세율, 고정사업장, 거주자 판정 등 국제거래 쟁점. 국내법 조문은 law_article, 국제조세 해석은 search_tax_rulings(tax='국조'). 반환: {국가, 발효일(현행 협정 — 조약 전문 기준), 서명일?, 최초 협정 발효일?(신협정으로 바뀐 조약), 관련 문서?, 종전 협정 문서?, 조문: [{조, 제목, 영문 제목, 본문}], 링크} — 조문 번호는 조약마다 다르니 keyword로 찾는 게 정확. 읽기 전용. 국세법령정보시스템 공개 조회(키 불필요), 같은 요청은 1일 캐시.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "tax_treaty"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
articleNo조문. 예: '제10조', '의정서'. 조약마다 번호 체계가 다르므로 주제로 찾을 땐 keyword 사용
countryYes체약국 이름(한글). 예: '미국', '중국', '일본', '베트남'. 모르면 아무 이름이나 넣으면 체결국 목록을 돌려줌
englishNoTrue면 영문 본문
keywordNo조문 제목·본문 검색어. 예: '배당', '고정사업장', '이자', 'dividends'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.1
    • changedInput schema / properties / lang / description
      Previous value: -"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'"New value: +"Output 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'"
  2. Addedv0.4.0

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, open-world and non-destructive behavior, but the description adds genuinely new operational facts: public lookup on 국세법령정보시스템 with no API key required and a 1-day cache for identical requests. It also warns that article numbering differs per treaty, which affects how the call should be made. Slight redundancy in restating '읽기 전용' 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.

Conciseness4/5

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

Well front-loaded with labeled '언제' and '반환' sections, so an agent can scan intent, alternatives and return shape quickly. It is slightly padded by restating the opening line in both English and Korean.

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 five parameters and no output schema, the description carries the return contract itself, listing fields like 국가, 발효일, 조문[{조, 제목, 영문 제목, 본문}] and 링크, plus caching and no-key access. Nothing essential for a correct call 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% and the schema already documents each parameter, including the country fallback that returns the partner list and the article-vs-keyword caveat. The description adds the response object shape but repeats rather than extends parameter meaning, so the baseline of 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 with scope: 'Read Korea's bilateral tax treaties (96 countries) article by article, Korean or English.' It immediately distinguishes itself from law_article (domestic statutes) and search_tax_rulings (interpretations) by naming both siblings.

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 '언제' block gives concrete trigger scenarios (non-resident withholding limited rates, permanent establishment, residency determination) and explicitly routes domestic-law questions to law_article and interpretation questions to search_tax_rulings(tax='국조'). When-to-use and when-to-use-something-else are both explicit.

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