mcp-tenki
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_forecastB | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as getting forecasts for Japanese locations, making it distinct by default.
The single tool follows a clear verb_noun pattern (get_forecast), which is consistent and predictable. Since there are no other tools, there is no inconsistency to evaluate.
One tool is too few for a weather forecasting server, as it lacks essential operations like searching locations, getting current conditions, or handling multiple forecast types. This minimal scope will likely cause agent failures due to incomplete functionality.
The server is severely incomplete for weather forecasting; it only provides forecasts without supporting related operations like current weather, alerts, or location validation. This creates significant gaps that will hinder agent workflows.