Skip to main content
Glama

Get Road Conditions & Advisories (Vegagerðin / Umferðin)

get_road_conditions
Read-onlyIdempotent

Returns live Icelandic road surface conditions, closures, weight restrictions, and regional advisories from IRCA / Vegagerðin (umferdin.is/graphql with gagnaveita.vegagerdin.is REST fallback), ranked with hazards first (max 20).

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 road segments to return (1-20, default 20).
hazards_onlyNoExclude 'Easily passable' road sections (default false).
route_or_regionNoOptional route number, pass, town, or region (e.g. '1', 'Route 41', 'Ring Road', 'Hellisheiði', 'South', 'Reykjanes', 'Westfjords', 'Highlands').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior, yet the description adds real value: data provenance and a GraphQL-with-REST-fallback source chain, hazards-first ordering, and a hard 20-result truncation cap. What is not disclosed is the shape of returned records or behavior when no segments match.

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 the resource and key behaviors first. The parenthetical endpoint detail (umferdin.is/graphql, gagnaveita.vegagerdin.is) is dense but earns its place as provenance/fallback disclosure.

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

Completeness4/5

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

For a three-optional-parameter read-only tool with no output schema, the description covers what is returned, ordering, truncation, and data source. It could say more about advisory content or empty-result behavior, but nothing essential to correct invocation 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 the schema already documents limit, hazards_only, and route_or_region with examples. The description only reinforces the limit cap and hazards-first ordering, adding little beyond structured data; baseline 3 is appropriate.

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?

Names a specific verb ('Returns') and a well-scoped resource: live Icelandic road surface conditions, closures, weight restrictions, and regional advisories. It is clearly distinguishable from the weather/earthquake/volcano siblings by domain, but it never explicitly contrasts itself with them (e.g. vs get_weather_warnings), so it stops short of a 5.

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?

Usage is only implied: 'live' signals real-time freshness and 'ranked with hazards first' hints at travel-safety triage, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer that this is the tool for road passability rather than general weather.

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