Skip to main content
Glama
seunguk3

local-tax-mcp

by seunguk3

search_reduction_ordinance

Search local government tax reduction and rate ordinances by municipality to verify exemptions and flexible tax rates before calculating local tax liability.

Instructions

지자체 감면조례·세율조례 검색(법제처 자치법규). 지방세는 조례가 탄력세율과 감면을 정하므로(지방세법 §111③, 지방세특례제한법 §4) 세액 결론 전 반드시 확인해야 한다. 국세 MCP에는 없는 축이다. 지자체명을 지정하면 정확도가 크게 오른다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ocNo
pageNo
queryNo추가 키워드. 예: 감면, 탄력세율, 재산세
regionNo지자체명. 예: 군포시, 경기도 군포시, 서울특별시 강남구
displayNo결과 수 1~100 (기본 20)
localTaxOnlyNo제명 기준 지방세 조례만 (기본 true)
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the tool's role in the tax workflow and cites the legal basis, implying this is a read-only search operation. However, it doesn't describe pagination behavior, result format, whether results come from a live API vs cache, or rate/auth considerations. The legal-citation context adds value but behavioral traits beyond search semantics are not disclosed.

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 a tight two-sentence paragraph that front-loads the core purpose (searching ordinances for tax reduction/rates) and packs legal citations and workflow context efficiently. The Korean text is dense but every clause earns its place, introducing the legal basis, the positioning relative to national tax tools, and the region-accuracy tip. Slightly dense for non-Korean readers but well-structured.

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?

This tool has meaningful complexity: no output schema, 6 parameters with 2 undocumented (oc, page), and no annotations. The description compensates reasonably by explaining the legal framework, workflow timing, and positioning against national tax tools. However, it doesn't clarify the return format (result count, fields), the meaning of oc and page parameters, or filtering semantics of localTaxOnly beyond schema text. Good for a search tool, but leaves the oc and page gaps unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% with 3 of 6 parameters described (query, region, display, localTaxOnly have descriptions; oc and page do not). The description adds strategic meaning beyond the schema: it emphasizes that specifying region (지자체명) significantly improves accuracy, which is the description's most actionable parameter guidance. It also frames query as keyword enrichment. However, oc and page remain undocumented in description, leaving some gap.

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+resource: searching municipal reduction ordinances and tax rate ordinances in the legal affairs bureau (법제처) local ordinance database. It clearly distinguishes from national tax MCP tools by noting this is a missing axis (축) not covered by national tax tools. However, it doesn't explicitly name sibling alternatives for differentiation, and the purpose is embedded in a dense two-sentence paragraph.

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?

The description provides clear context on when to use: before concluding tax amounts (세액 결론 전 반드시 확인), because local taxes rely on ordinances for flexible rates and exemptions per specific legal provisions (지방세법 §111③, 지방세특례제한법 §4). It notes specifying the municipality (지자체명) greatly improves accuracy. It doesn't explicitly state when NOT to use it or name alternatives, but the timing guidance is unusually specific and actionable.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/seunguk3/local-tax-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server