Skip to main content
Glama
jalateras

weather

by jalateras
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_alertsA
    Get active weather alerts for a state.

    Args:
        state: Two-letter state code (e.g., 'CA', 'NY')

    Returns:
        Formatted alerts or error message
get_forecastC
    Get weather forecast for coordinates.

    Args:
        latitude: Latitude coordinate
        longitude: Longitude coordinate

    Returns:
        Formatted forecast or error message
run_shell_commandC
    Run a shell command and return the output.

    Args:
        command: Shell command to execute

    Returns:
        Command output or error message

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
processes://top
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.8/5.0

Scored across 3 tools

Disambiguation2/5

The two weather tools (get_alerts, get_forecast) are distinct, but the inclusion of run_shell_command is completely unrelated, making the toolset confusing. An agent might struggle to decide when to use the shell command versus the weather tools, and the server's purpose is unclear.

Naming Consistency3/5

The naming pattern is consistent (verb_noun) across all tools, but run_shell_command disrupts the domain-specific naming expected for a weather server. The pattern itself is fine, but the mismatch in domain reduces consistency.

Tool Count2/5

Three tools is reasonable for a simple weather server, but the presence of run_shell_command makes the count inappropriate because it does not fit the server's purpose. The toolset should focus solely on weather operations.

Completeness2/5

The weather tools cover alerts and forecasts, but miss common operations like current conditions or historical data. Moreover, the shell command is out of place and does not contribute to weather functionality, leaving a gap in the expected weather domain coverage.

Resources