Skip to main content
Glama

get_road_conditions

Read-onlyIdempotent

Get live road conditions in Iceland from Vegagerðin.

Returns condition (Easily passable, Slippery, Snow, Closed, etc.) for
road segments matching the query. Omit road_name for major tourist routes
(Ring Road, Golden Circle, South Coast).

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_road_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of road segments to return. Default 20.
routeNoRoute number to filter, e.g. 1 for Ring Road, 35 for Geysir road, 36 for Þingvellir. Omit for text-based search or major routes.
road_nameNoRoad or area name to search for, e.g. 'Hringveg' (Route 1), 'Vík', 'Skógafoss', 'Þingvellir'. Omit to get all major tourist routes.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the data source and the condition vocabulary (Easily passable, Slippery, Snow, Closed), which helps interpretation, but says nothing about freshness, caching, or behavior on zero matches.

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?

Three short sentences with the core purpose front-loaded and no filler. The final routing hint overlaps with the schema text, which is the only real waste.

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?

Return values are covered by the existing output schema and safety behavior by the annotations, so the description only needs to establish purpose, source, and query strategy — all of which it does. Nothing needed to invoke this read-only tool correctly is missing.

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

Parameters3/5

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

Schema coverage is 100%, so all three parameters are already documented, including the route-number examples and the 'omit for major routes' note. The description's road_name hint largely restates what the schema says, adding little new meaning beyond the baseline.

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 opens with a specific verb and resource ('Get live road conditions in Iceland') and names the data source, Vegagerðin. An agent can distinguish this from get_weather or get_safety_alerts by the resource alone, though no sibling is named explicitly.

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?

There is real guidance on how to query ('Omit road_name for major tourist routes'), but no statement of when to prefer this tool over adjacent ones like get_weather or get_safety_alerts. Usage is implied by the resource rather than spelled out.

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.

Resources