Skip to main content
Glama

Crosby, TX Weather

by com.crosbynews

Current conditions

get_current_conditions
Read-onlyIdempotent

Current weather for Crosby, TX: temperature, feels-like, sky, precip chance, humidity, dew point, UV index, measured air quality (EPA/AirNow, Houston metro area), and sunrise/sunset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
uvNoEPA UV index; null at night or when the EPA feed is down.
sunNo
currentNoAn NWS forecast period, passed through (startTime, temperature, shortForecast, windSpeed, probabilityOfPrecipitation, ...) plus computed feelsLike °F where applicable. Full schema: https://crosbynews.com/openapi.json Adds dewpointF and humidityPercent.
updatedNoISO 8601 timestamp of the last data refresh.
locationYes
airQualityNoUS AQI. measured:true = EPA/AirNow monitors (Houston metro reporting area incl. Crosby); measured:false = Open-Meteo modeled fallback. Regional, not Crosby-pinpoint either way.

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint, idempotentHint, etc. Description adds specific data sources (EPA/AirNow for Houston metro area) and includes sunrise/sunset, which are not obvious from annotations. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence listing all key outputs. Every word adds value. Extremely concise and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has output schema, and description covers all listed data fields. Scope (Crosby, TX) is clear. No further details needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters, so schema coverage is 100% by default. Description does not need to add parameter info. Baseline 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it provides current weather conditions for Crosby, TX, listing specific metrics (temperature, feels-like, sky, etc.). This distinguishes it from sibling tools like get_forecast (future) and get_air_quality (air quality only).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when to use or alternatives are given. However, the listed data points imply it's for a comprehensive current snapshot. An agent can infer usage from sibling tool names but description lacks direct guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crosby, TX Weather toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

All tools have clearly distinct purposes: alerts, news, conditions, emergency contacts, forecast, radar, river levels, school events, traffic, and tropical outlook. There is no overlap or ambiguity.

Naming Consistency5/5

All tool names follow the consistent pattern 'get_<topic>' using snake_case (e.g., get_alerts, get_forecast, get_radar). No deviations.

Tool Count5/5

With 10 tools covering a broad range of local information (weather, alerts, news, emergency, traffic, schools, etc.), the count is well-scoped and each tool earns its place.

Completeness5/5

The tool set comprehensively covers the domain of local weather and community info for Crosby, TX: current conditions, forecasts, alerts, radar, river levels, tropical outlook, traffic, school events, news, and emergency contacts. No obvious gaps.

Resources