Jira MCP
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_weatherA | Retrieves weather forecast information from the National Weather Service API for the specified location. The location should be in the format of latitude,longitude (e.g., '47.7623,-122.2054'). |
| get_alertsA | Retrieves all currently active weather alerts, warnings, and advisories issued by the National Weather Service for the specified state. This includes severe weather warnings, flood advisories, winter weather alerts, and more. |
| get_forecastA | Retrieves a multi-period weather forecast from the National Weather Service for the specified coordinates. The forecast includes temperature, wind conditions, and detailed descriptions for the next 5 forecast periods (typically covering the next 2-3 days). |
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 3 tools
The tools have significant overlap and ambiguity, as 'get_forecast' and 'get_weather' both retrieve weather forecasts from the National Weather Service for specified locations, making them easily confused. Only 'get_alerts' has a clearly distinct purpose focused on active alerts and warnings, but the other two tools lack clear boundaries.
All tool names follow a consistent 'verb_noun' pattern with 'get_' prefix and snake_case formatting, making them predictable and readable. There are no deviations in naming conventions across the three tools.
With only 3 tools, the set feels too thin for a server named 'Jira MCP', which suggests a project management or issue-tracking domain, but the tools are all weather-related. This is an extreme mismatch between the server name and the tool scope, indicating poor appropriateness.
The tool surface is severely incomplete for the inferred domain from the server name 'Jira MCP', which should cover Jira-related operations like issues, projects, or workflows. Instead, it only provides weather data retrieval with no CRUD or lifecycle coverage for Jira, leaving obvious gaps that will cause agent failures.