MCP Server Example
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 |
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 2 tools
The two tools have clearly distinct purposes: one retrieves weather alerts for a state, and the other retrieves weather forecasts for a location. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the need for alerts versus forecasts.
Both tools follow a consistent verb-noun pattern with hyphens (get-alerts, get-forecast), using the same verb 'get' and descriptive nouns. This predictable naming scheme enhances readability and reduces confusion for agents.
With only two tools, the server feels thin for a weather domain that typically involves more operations, such as current conditions, historical data, or radar imagery. This limited set may not fully support comprehensive weather-related tasks.
The tool set is severely incomplete for a weather server, lacking essential operations like getting current conditions, historical weather data, or radar images. This creates significant gaps that could lead to agent failures in handling broader weather queries.