Skip to main content
Glama

Crosby, TX Weather

by com.crosbynews

Roads & traffic

get_traffic
Read-onlyIdempotent

Live traffic incidents and scheduled lane closures on the roads Crosby, TX drives — US-90, FM-2100, FM-1942, and the Crosby stretch of IH-10 East — from Houston TranStar, plus links to the corridor traffic cameras. High-water road reports appear here during floods. Empty lists mean quiet roads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaYes
sourceYes
camerasNoCorridor cameras — pageUrl links TranStar's own camera pages (images are not embedded).
updatedNoISO 8601 timestamp of the last data refresh.
incidentsNoEmpty = no monitored incidents (the normal state); null = the incidents feed was unreachable at the last refresh.
liveMapUrlNo
laneClosuresNoScheduled closures; empty = none, null = feed unreachable at the last refresh.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds data source, camera links, and behavior for empty lists ('Empty lists mean quiet roads') and flood reporting. No contradictions.

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 plus a brief note on empty lists. Every part adds value; no fluff. Front-loaded with key action and scope.

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?

Given zero parameters and an output schema, the description fully covers purpose, behavior, and data sources. Complete for this tool's capabilities.

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; baseline for 0 params is 4. Description adds meaning about what the tool returns (e.g., incident types, camera links, flood reports), which is helpful beyond the empty schema.

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?

Clearly states the tool returns live traffic incidents, scheduled lane closures, and high-water reports on specific roads (US-90, FM-2100, etc.) with source (Houston TranStar) and camera links. Distinct from siblings like get_air_quality or get_alerts.

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?

Implies usage for traffic info on specific roads, but no explicit when-to-use or when-not-to-use compared to siblings. No alternative tools mentioned.

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