ASP.NET MCP Server providing weather forecast tools via HTTP transport
This server has a single tool with significant definition quality gaps. The tool name 'GetWeatherForecastCity' uses PascalCase (C# convention) rather than snake_case (MCP convention), and while it starts with a verb, it's not optimized for LLM parsing. The description is extremely sparse (10 characters in Japanese, untranslated), violating the 10-1024 character guideline and failing to explain WHAT the tool does, WHEN to use it, or what it returns. The input parameter 'citycode' has a description that is garbled Japanese text and provides no clear guidance on valid formats, ranges, or how to obtain a city code. Most critically, there is no documented output schema, the tool returns a raw string concatenation, and LLMs cannot plan downstream operations without knowing the response structure. The tool is read-only (low risk), but lacks all the structural patterns needed for reliable agentic use.
取得天気情報
Tool name uses PascalCase instead of snake_case; not optimized for LLM verb parsing
Tool description is 10 characters of garbled Japanese text; does not explain what the tool does, when to use it, or what it returns
Parameter 'citycode' description is garbled Japanese with no actionable guidance; does not explain valid formats, ranges, or how to obtain a city code
No output schema documented; tool returns unstructured string; LLMs cannot plan downstream operations or extract structured data
No error handling guidance; tool calls EnsureSuccessStatusCode() but does not catch or translate HTTP errors into actionable recovery messages
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 26 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 32 | - | v1 |