Skip to main content
Glama

get_route_conditions

Read-only

Weather, traffic and road-condition summary for a route or corridor.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_route_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
corridorNo
route_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds almost no behavior beyond them — it does not say how current the conditions are, whether it covers the full corridor or sampled points, or how the three domains are combined.

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

Conciseness4/5

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

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity is part of why key invocation details are missing.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but the tool is an aggregator with two optional, apparently alternative parameters and the description resolves neither the selection ambiguity nor the freshness/coverage semantics. For this level of schema ambiguity the description leaves too much open.

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

Parameters1/5

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

Schema description coverage is 0% and there are two parameters ('corridor' and 'route_id'), yet the description only echoes the words 'route or corridor' without explaining the difference, whether they are mutually exclusive, or which to supply. With zero required parameters, the agent gets no help deciding what a valid call looks like.

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

Purpose4/5

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

The description names a concrete resource and scope: an aggregated weather, traffic and road-condition summary for a route or corridor. That distinguishes it from single-domain siblings like get_current_weather, get_traffic_congestion and get_road_incidents, even though it is phrased as a noun phrase with no verb.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this composite tool over querying the individual weather/traffic/incident tools, and no mention of prerequisites, ordering, or when not to use it. The agent must infer its role from the phrase 'summary'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.