Skip to main content
Glama
Sign In
here-hgv-mcp

here-hgv-mcp

by craigst
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

HERE traffic flow (speeds and jam factor)

here_traffic_flow
Read-only

Retrieve live traffic flow for roads in a bounding box, circle, or corridor, returning jam factor, speed, confidence, and traversability per segment to assess HGV congestion and route risk.

Instructions

Read live traffic flow for roads within a bounding box, circle or corridor using HERE Traffic API v7. Returns jamFactor (0 = free flow, 10 = blocked), current speed, uncapped speed, free-flow speed, confidence and traversability per road segment, plus a location description and OLR reference. locationReferencing is MANDATORY for flow (default ["olr"]). maxJamFactor defaults to 10 so congestion is NOT hidden (HERE's own default of 1.0 would only return free-flowing roads). For HGV route risk assessment: average jam factor and count of jams ≥5 across the corridor is a quick congestion indicator before calling here_route. Note: HERE returns all matching segments; limit truncates the returned list only.

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": "here_traffic_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoCentre "lat,lng" for a circular area. Requires radiusM.
bboxNoBounding box [west, south, east, north] in degrees, e.g. [-2.35,53.42,-1.50,53.83] for Greater Manchester.
limitNoMaximum flow segments to return (default 100).
radiusMNoRadius in metres for the circular area around "at" (used only with at).
maxJamFactorNoOnly segments with jam factor ≤ this (default 10 = include congestion; HERE default 1 would hide jams).
minJamFactorNoOnly segments with jam factor ≥ this (default 0).
corridorRadiusMNoCorridor half-width in metres (used only with corridorPolyline).
advancedFeaturesNoHERE advanced features (may be billed separately by HERE).
corridorPolylineNoHERE Flexible Polyline for a corridor filter (e.g. a here_route includePolyline result). Requires corridorRadiusM.
functionalClassesNoFilter to road functional classes (1 = motorways; 1-3 keeps the HGV trunk network).
locationReferencingNoLocation referencing scheme(s); flow requires at least one (default ["olr"]).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnly and open-world; the description adds genuinely non-obvious behavior: HERE's own maxJamFactor default of 1.0 would hide congestion so this tool overrides to 10, locationReferencing is mandatory for flow, and limit truncates only the returned list while HERE still matches all segments. Those disclosures materially change how an agent will call the tool.

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?

Front-loaded with purpose and query modes, then defaults and caveats, with zero filler sentences. It is dense with parentheticals and slightly long, but every clause carries information an agent needs.

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?

Eleven loosely-constrained optional parameters and no output schema, yet the description covers the geometry modes, the mandatory location referencing, the truncation semantics, and enumerates the returned fields (jamFactor, speed, free-flow speed, confidence, traversability, OLR). Nothing needed to call it correctly is missing.

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?

Schema coverage is 100%, so parameter meanings are already documented; the description still adds interpretation of the jamFactor scale (0 free flow to 10 blocked) and the consequence of the maxJamFactor default. It does not add much on the circle/corridor pairing rules beyond what the schema says, so it sits just above the baseline.

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?

States a specific verb (read live traffic flow), a specific resource (road segments via HERE Traffic API v7), and the three supported spatial filters (bbox, circle, corridor). It is immediately distinguishable from here_traffic_incidents and here_route by naming flow data and its geometric query modes.

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

Usage Guidelines4/5

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

Gives a concrete use case and ordering: use jam-factor aggregates across a corridor as a congestion pre-check before calling here_route, which explicitly routes the agent relative to a sibling. It also states the locationReferencing prerequisite. It lacks an explicit when-not-to-use statement versus here_traffic_incidents, which prevents a 5.

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

Deploy Server

Other Tools