This server has severe definition quality issues. The tool list contains 8 entries, but only 3 unique tools exist (get_alerts, get_forecast, get_logs), with duplicates in English and Chinese. All tools have minimal descriptions (10-60 chars), lack comprehensive parameter documentation, and have no visible output schema definitions. The server uses STDIO transport (not remotely accessible) and demonstrates poor tool composition hygiene with duplicate tool names. Parameter descriptions exist but are generic (e.g., 'Two-letter US state code'). No error handling patterns are visible, no tool annotations (readOnlyHint is present in metadata but not in tool definitions), and no security considerations documented despite tools accepting external parameters.
獲取美國特定州份的警報資料.
Get weather alerts for a US state.
Get weather alerts for a US state.
獲取特定位置的預報資料
Get weather forecast for a location.
Get weather forecast for a location.
Get the logs of the weather tool.
Get the logs of the weather tool.
Duplicate tool definitions: get_alerts, get_forecast, and get_logs each appear 2-3 times (once in English, once in Chinese, and sometimes repeated). This violates the composition principle that each tool should have exactly one canonical definition. LLMs will be confused by multiple identical tools with different language descriptions.
All tool descriptions are under 60 characters and lack context. 'Get weather alerts for a US state' does not explain WHEN to call this tool vs others, what the return structure is, or how it relates to get_forecast. Per pattern:tool-description, descriptions should be 50-200 chars and answer: What does it do? When to use it? What does it return?
Output schemas are not documented anywhere in the source code. No response structure is defined for get_alerts, get_forecast, or get_logs. Per pattern:response-shaper, LLMs need to know what fields to expect (e.g., does get_alerts return an array of alert objects? What fields? timestamps? severity levels?). Without this, the LLM cannot plan downstream tool calls or extract the right data.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 45 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 34 | - | v1 |
Parameter descriptions are minimal and lack format guidance. For 'state' parameter: 'Two-letter US state code (e.g. CA, NY)' does not document whether the input is case-sensitive, whether territories (PR, VI) are accepted, or what error is returned for invalid codes. Per pattern:constrained-input, the description should define the constraint explicitly or use an enum.
No error handling guidance visible. If get_alerts is called with an invalid state code, what happens? Does it return 400? 404? An empty array? Does it suggest valid states? Per pattern:recovery-guide, error responses must guide the LLM on what to do next, not just fail.
Tool definitions use string descriptions for parameters, but no type constraints (minLength, maxLength, pattern) are visible. For 'latitude' and 'longitude', no validation rules are shown (e.g., latitude -90 to +90, longitude -180 to +180). Per pattern:constrained-input, numeric ranges and formats must be explicit in the schema.
Mixed-language tool definitions (English and Chinese) with identical names create namespace pollution. Clients cannot distinguish between 'get_alerts' in English and 'get_alerts' in Chinese if both are registered. Either dedup into one tool with a single description or use language-qualified names (e.g., get_alerts_en, get_alerts_zh).