Skip to main content
Glama

Lifelaw Korean Law (라이프로 법령)

Search tax interpretations (세법 해석 검색)

search_tax_interpretation
Read-onlyIdempotent

Search Korean tax interpretations (advance rulings, replies to inquiries, 예규, etc.) by the National Tax Service (국세청) and the Ministry of Economy and Finance (재정경제부) by words in the title (in the body with body_search), newest first. Search terms must be in Korean. Put a result's document ID (문서ID) into get_tax_interpretation to read it. Without agency, both agencies are searched. Interpretations are not law but reference material.

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": {
      "query": "<query>"
    },
    "name": "search_tax_interpretation"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page number (from 1). Default 1
queryYesKorean words in the title. E.g. 양도소득세 비과세, 부가가치세 면세
agencyNo국세청 = National Tax Service (NTS) / 재정경제부 = Ministry of Economy and Finance (MOEF). Default: both
body_searchNotrue: search the body instead of the title

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / agency / description
      Previous value: -"해석 기관. 생략하면 국세청·재정경제부 모두"New value: +"국세청 = National Tax Service (NTS) / 재정경제부 = Ministry of Economy and Finance (MOEF). Default: both"
    • changedInput schema / properties / body_search / description
      Previous value: -"true 면 안건명 대신 본문에서 찾습니다"New value: +"true: search the body instead of the title"
    • changedInput schema / properties / page / description
      Previous value: -"검색 결과 쪽 번호(1부터). 생략하면 1"New value: +"Result page number (from 1). Default 1"
    • changedInput schema / properties / query / description
      Previous value: -"안건명에 들어갈 단어. 예: 양도소득세 비과세, 부가가치세 면세"New value: +"Korean words in the title. E.g. 양도소득세 비과세, 부가가치세 면세"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds genuine traits beyond them: results are ordered newest first, the query must be in Korean, and interpretations are reference material rather than law — a caveat an agent needs to interpret results responsibly.

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?

The description is front-loaded with the core action and packs ordering, the Korean-language constraint, the follow-up tool, and the agency default into a few tight sentences. It is slightly redundant in restating the schema's 'both agencies by default' behavior, keeping it from a 5.

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?

With no output schema, the description carries the return-value burden and does so adequately by explaining ordering and by pointing to get_tax_interpretation for full document reads. It does not describe the shape of search results or pagination beyond the schema's page parameter, leaving a small gap.

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 four parameters are already documented in the schema, including the agency enum and the body_search toggle. The description largely restates those semantics (Korean-only query, both agencies by default) without adding syntax, format, or matching-behavior detail, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — searching Korean tax interpretations from NTS and MOEF by title words — and adds scope details (newest first, title vs body). It does not differentiate itself from the sibling search_interpretation, which an agent would also see in the tool list, so it falls short of a 5.

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

Usage Guidelines4/5

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

It gives concrete usage context: use body_search to search the body instead of the title, omit agency to search both, and pass a result's 문서ID to get_tax_interpretation to read the full document. It never says when to prefer search_interpretation or another sibling, so it stops short of explicit alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources