Data4Library MCP Server
Related Servers
Alternatives to Data4Library MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceSearches for children's programs at public facilities like libraries and cultural centers in South Korea, answering natural language queries about schedules, fees, and registration.-
- AlicenseNot gradedqualityDmaintenanceEnables AI to query real-time Korean public data including weather, real estate prices, air quality, economic indicators, and business registration via natural language.1MIT
- AlicenseAqualityBmaintenanceSearch and collect data from the National Assembly Library of Korea's OpenAPI (21 DB types) and export to xlsx/csv/json/sqlite.61MIT
- AlicenseNot gradedqualityAmaintenanceEnables exploration of Korean National Assembly data by connecting bills, committee reviews, and official records. Allows users to ask natural language questions and receive structured answers with citations to original documents.26Apache 2.0
- -licenseNot gradedqualityNot gradedmaintenanceEnables searching and retrieving Korean legal information including laws, court precedents, legal interpretations, and local ordinances from the Korean National Law Information Center API with intelligent search ranking.-
- AlicenseNot gradedqualityDmaintenanceEnables exploration and interaction with South Korea's Public Data Portal (OpenAPI) through keyword search, standard documentation retrieval, and direct API endpoint calls with automatic service key injection.11Apache 2.0
TDQS
Scored across 27 tools
Several tools have heavily overlapping purposes, especially search_popular_books, search_popular_books_by_library, and get_popular_books_by_library, which all concern popular loan books with unclear differences. The code-related tools (get_subject_codes, get_detailed_subject_codes, search_detailed_kdc_codes) and library-search variants also blur boundaries.
All names use snake_case and mostly follow a verb_noun structure, but the use of get_ vs search_ is inconsistent and doesn't clearly separate semantics (e.g., search_popular_books vs get_popular_books_by_library). The naming is readable but lacks a consistent rule.
27 tools exceeds the 25 threshold for 'too many' for a single server. The count is inflated by redundant variations (three popular-book tools, multiple code-list/search tools) that could be consolidated.
The set covers the read-only library domain well: library search, book search/detail, availability, popular books, recommendations, usage trends, and code lookups. There are minor gaps such as no direct tool to search by a specific date range or comprehensive library comparison, but agents can work around them.