Related Servers

Most domain areas are cleanly separated by search/get pairs and labels, but the tool set is so large that boundary cases are fuzzy: get_daily_term and get_daily_to_legal are near-duplicates, and get_legal_term_kb/search_legal_terms plus the public-institution vs ALIO rule tools can be confused. An agent can usually disambiguate with detailed descriptions, but the misselection risk is elevated.

Tool names overwhelmingly use snake_case and follow a predictable search_/get_/compare_/suggest_/analyze_/chain_ + domain pattern. The bracketed Korean domain labels and repeated conventions such as search_ for lookup and get_..._text for full text make the surface highly consistent.

110 tools far exceeds reasonable MCP tool limits and matches the explicit extreme-overload threshold. Many operations are simple search/get pairs or chain shortcuts that could be consolidated into parameterized tools, so the count creates avoidable decision cost for agents.

For a read-only legal research domain, the server covers the full research lifecycle: law identification, retrieval, article-level detail, comparisons, history, annexes, precedents, interpretations, administrative decisions, rulings, and public-institution regulations. There are no obvious dead ends; starting with a keyword, vague term, document, or article can lead to the relevant legal materials.