Skip to main content
Glama
shreyyzsh

Claude-NWS Protocol Bridge

by shreyyzsh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_alertsA
Getting weather alerts for a US State.

Args:
    state: two-letter us state code (e.g CA, NY)
get_forecastC
Getting weather forecast for a location.

Args:
    latitude: latitude of the location
    longitude: longitude of the location

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

B3.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: get_alerts retrieves weather alerts for a US state, while get_forecast provides weather forecasts for a specific geographic location. There is no overlap in functionality or ambiguity between them.

Naming Consistency5/5

Both tools follow a consistent verb_noun naming pattern (get_alerts and get_forecast), using the same verb 'get' followed by a descriptive noun. This makes the tool set predictable and easy to understand.

Tool Count2/5

With only two tools, the server feels thin for a weather service domain. While the tools cover alerts and forecasts, there are likely missing operations such as current conditions, radar data, or historical data that would make the set more complete for typical weather-related tasks.

Completeness2/5

For a weather service, the tool set is significantly incomplete. It lacks core functionalities like getting current weather conditions, radar or satellite imagery, historical data, or air quality information. This limited coverage will likely cause agent failures when trying to perform comprehensive weather-related tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources