Weather & WordPress 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-alertsC | Get weather alerts for a state |
| get-forecastC | Get weather forecast for a location |
| get-latest-postsA | Get the 10 most recent posts from hafiz.blog (WordPress.com) |
| get-categoriesB | Get all categories available on hafiz.blog (WordPress.com) |
| get-posts-by-categoryC | Get posts from a specific category on hafiz.blog (WordPress.com) |
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 5 tools
The tools are clearly split into two domains (weather and WordPress), but within each domain there is some overlap. For weather, get-alerts and get-forecast both provide weather information but for different purposes, which could cause confusion. For WordPress, get-latest-posts and get-posts-by-category both retrieve posts but with different filters, which might lead to misselection if the agent isn't clear on the distinction.
All tool names follow a consistent verb_noun pattern with hyphens (get-alerts, get-categories, get-forecast, get-latest-posts, get-posts-by-category). This makes them predictable and easy to understand, with no deviations in style or convention across the set.
With 5 tools, the count is reasonable, but it feels thin for covering two distinct domains (weather and WordPress). Each domain only has 2-3 tools, which might not provide enough functionality for comprehensive workflows in either area, making it borderline appropriate.
There are significant gaps in both domains. For weather, there's no way to get current conditions or historical data, limiting coverage. For WordPress, there are no tools for creating, updating, or deleting posts or categories, making it read-only and incomplete for typical content management tasks.