Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get-alertsC

Get weather alerts for a US state

get-forecastB

Get weather forecast for a location in the US

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools target clearly different resources: alerts (hazard notifications) versus forecast (predicted conditions). There is no plausible scenario where an agent would confuse them.

Naming Consistency5/5

Both tools follow an identical get-<resource> pattern in kebab-case. The convention is predictable and would extend cleanly if more tools were added.

Tool Count3/5

Two tools is on the thin side for a weather server; there is no tool for current observations, hourly data, or location lookup. Each tool earns its place, but the surface feels minimal rather than well-scoped.

Completeness3/5

Core weather use cases (alerts and forecast) are covered, but notable operations are missing: current conditions, hourly forecasts, and any way to resolve a place name to coordinates. Agents can work around this with external knowledge but will hit dead ends for common requests.

Maintenance

ActivityInactive
ResponsivenessNo recent community issues