Collection of 8 Model Context Protocol servers built with Kotlin and Quarkus framework, including weather data, date/timezone operations, Excel file handling, filesystem access, Taiwan stock data, and Google integrations
This MCP server collection exhibits significant definition quality gaps. Tool names are action-verb-oriented and reasonably clear (get*, create*, delete*, read*, write*, etc.), but descriptions are inconsistent, some are specific while others are generic or incomplete. Parameter schemas are present but many lack detailed constraints, type specifications beyond basic types, and dependency documentation. Output schemas are not documented. Error handling guidance is absent. The server implements 21 tools across 8 Quarkus modules (cwa-tw weather, date/timezone, excel, filesystem), but the codebase review reveals incomplete tool registration patterns and missing structured output specification. Most tools score in the 35-50 range; no tools achieve A-level (80+) quality.
Add a new worksheet
Convert date time from one time zone to another
Create a new Excel file
Delete a worksheet
Export worksheet data to CSV file
Get all available time zone IDs
Get API ID corresponding to Taiwan cities/counties
Get common time zones by region
Get current date time in specified time zone, default date formate is yyyy-MM-dd HH:mm:ss
Output schemas completely undocumented. No tool specifies what fields, types, or structure it returns. LLMs cannot plan downstream tool calls or extract required data for chaining.
Minimal or missing error handling guidance. No tool describes what to do if an operation fails, whether errors are retryable, or how to recover. Errors like 'file not found' or 'invalid timezone' return no actionable recovery hints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 42 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 35 | - | v1 |
Get earthquake observation data for a specific area. AreaName is required. Time can only be set before the current time, and the time range cannot exceed 36 hours.
Get current date
Get weather forecast data for all townships in Taiwan. LocationName is required. TimeFrom must be before TimeTo, and TimeTo cannot exceed TimeFrom by more than 24 hours.
Import CSV data into an Excel worksheet
Check if given date is today
List all worksheets in an Excel file
Merge cells in a worksheet
Read data from a cell
Read data from a row
Rename a worksheet
Write data to a cell
Write data to a row (comma-separated values)
Sparse parameter constraints. Many parameters lack minimum/maximum bounds, enums, regex patterns, or format specifications. E.g., 'filePath' parameter has no validation hint; 'rowIndex' has no bounds (0-based but upper limit unknown); timezone parameters lack enum list.
Destructive operations (deleteWorksheet, mergeCells) lack confirmation or dry-run support. No mention of whether operations are reversible or require user approval before execution.
Tool descriptions are generic or incomplete. Many describe only the basic action (e.g., 'Add a new worksheet') without context on WHEN to call, dependencies, or side effects. No descriptions mention whether tools are idempotent, state-modifying, or have prerequisites.
Missing parameter interdependencies and constraint documentation. timeFrom/timeTo parameters require relationship documentation ('TimeFrom must be before TimeTo, TimeTo cannot exceed TimeFrom by more than 24 hours') but this is buried in description; no formal schema-level constraints present.
No pagination support documented. Tools like listWorksheets and getCommonTimeZonesByRegion that potentially return multiple items lack limit, offset, or cursor parameters. Large result sets could exhaust context windows.
Risk levels assigned (READ_ONLY, WRITE, DESTRUCTIVE, REVERSIBLE) are present but not reflected in tool annotations or descriptions. LLMs cannot infer which operations are safe to retry.