Skip to main content
Glama

commutescout

by io.github.nicglazkov

check_region

Read-only

Full current-conditions report for a California region.

Use this for area-scale questions ("how is the Bay Area?", "what's
happening in SoCal?") instead of stitching together point queries. It
sweeps every source over the whole region at once: CHP incidents
(severity-sorted, worst first), lane closures in place (full closures
called out), chain controls, and wildfires inside the region.

Regions: Bay Area, Sacramento metro, Tahoe/Sierra, Central Valley,
Southern California, San Diego, Central Coast, North State. An
unrecognized region name returns the list.

Large regions are capped to the most severe items; the counts are
always exact and the response says when a list was truncated.
Freshness: CHP ~1/min fetched live, everything else 5-minute cache.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Adds significant behavioral context beyond annotations: sweeps all sources, severity-sorted incidents, full closure callouts, capping for large regions with exact counts and truncation notice, and freshness details (CHP live, others 5-min cache). Contradicts nothing in annotations.

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?

Concise, well-structured, and front-loaded. First sentence states core purpose. Subsequent lines list contents, regions, and edge cases. Every sentence earns its place with no redundancy.

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?

For a complex tool covering multiple data sources with truncation and caching, the description fully explains behavior, output contents, and limitations. No output schema needed as description covers return structure.

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

Parameters5/5

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

Only parameter 'region' is detailed with a list of recognized values (Bay Area, Sacramento metro, etc.) and behavior for unrecognized input. Schema says only type 'string', so description adds essential semantic meaning.

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 a full current-conditions report for a California region, differentiating it from point-query siblings like get_incidents or check_route. It specifies the verb 'check' and resource 'region', and explicitly contrasts with stitching together point queries.

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

Usage Guidelines5/5

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

Explicitly tells when to use: for area-scale questions ('how is the Bay Area?', 'what's happening in SoCal?') and recommends it over multiple point queries. Also notes that an unrecognized region name returns the list, providing guidance on error handling.

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

All commutescout 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.7/5.0
Disambiguation5/5

Each tool targets a distinct aspect of road conditions: region summary, route-specific, cameras, chains, incidents, closures, out-of-state, signs, wildfires, and ranking. Even related tools like check_region and check_route have clear, differentiated purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (check_region, check_route, get_cameras, etc.). The verbs 'check' and 'get' are used appropriately for different actions, maintaining predictability.

Tool Count5/5

With 10 tools, the server is well-scoped. Each tool provides a specific, non-redundant function for the domain of California road conditions, fitting perfectly within the ideal 3-15 range.

Completeness4/5

The tool set covers major aspects: incidents, closures, chains, wildfires, cameras, signs, and region/route summaries. Missing dedicated traffic flow/speed data or construction schedules, but overall robust for trip planning and condition awareness.

Resources