pollen-alert-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your Ambee API key |
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_pollen_forecastB | Get pollen levels (tree, grass, weed) and species-level risk for a specific latitude and longitude. |
| get_coordinatesA | Convert a place name into latitude and longitude. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_pollen_risk | Instructs the AI to analyze pollen data and provide medical-grade context. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Hayfever Mitigation Guide | Tips and strategies for reducing allergy symptoms based on pollen levels. |
| Allergen Information | Information about different types of pollen and their peak seasons. |
TDQS
Scored across 2 tools
Each tool has a distinct purpose: one converts place names to coordinates, the other retrieves pollen forecasts using coordinates. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern with snake_case (get_coordinates, get_pollen_forecast), making them predictable and easy to understand.
With only two tools, the server feels slightly thin, but it covers the essential workflow for a pollen alert service: location lookup and forecast retrieval. The count is reasonable for a focused domain.
The server provides the core functionality needed to get pollen alerts by location. A minor gap is the lack of a direct place-name-to-forecast tool, but the separate steps are logically sound.