Weather & HR Management MCP Server
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| askWeatherD | – |
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 agent cannot misselect among multiple options since only 'askWeather' exists.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or conventions. The name 'askWeather' stands alone without any inconsistencies.
The server name 'Weather & HR Management MCP Server' suggests a broad scope covering both weather and HR domains, but only one tool is provided. This is a significant mismatch, as a single tool cannot adequately cover such diverse functionalities, making it too few for the apparent scope.
The server implies coverage of weather and HR management, but only a weather-related tool is present, with no HR tools at all. This represents a severe gap, as the tool surface is incomplete for the stated purpose, likely causing agent failures in HR-related tasks.