Skip to main content
Glama

Road traffic counts by station, road or canton

get_traffic_counts
Read-only

Retrieve annual average traffic counts from FEDRO automatic stations; filter by station, road, or canton, sort by daily volume or heavy-goods share, or rank stations nationwide by daily volume.

Instructions

Annual average traffic from FEDRO's automatic counting stations: vehicles per day (all days and weekdays), morning and evening peak hours, day and night hourly averages, and heavy-goods share. Filter by station or place name, road (A1, A 2, H 18) or canton (UR, GR, …); sorted by daily volume or heavy-goods share. With no filter it ranks the busiest stations nationwide. Examples: {station:'Gotthard'}, {road:'A1', canton:'ZH'}, {sort_by:'heavy_share'}.

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

Input Schema

NameRequiredDescriptionDefault
roadNoRoad designation, e.g. A1, A 13, H 18
limitNo
cantonNoTwo-letter canton code, e.g. UR
sort_byNodaily
stationNoStation or place name, partial (e.g. 'Gotthard', 'Muttenz')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered upstream. The description adds meaningful domain behavior beyond that — what 'annual average traffic' actually means (all days vs weekdays, peak vs off-peak, heavy-goods share) and what happens with zero filters. It does not address result-size limits, pagination, or data vintage/coverage years, so it adds context without fully characterizing the response.

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?

Two sentences, no filler, with the metric inventory front-loaded and filters/examples after. The first sentence is heavily packed with a long en dash list, which is dense but still scannable; all content earns its place.

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?

With no output schema and five optional parameters, the description must carry the burden of telling the agent what comes back — it does so by enumerating the measurement types and stating the default ranking. The main residual gap is the absence of any statement about the shape of results (a ranked list of stations) or the limit parameter's effect. Adequate for correct invocation.

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?

With 60% schema coverage, the description meaningfully compensates: it clarifies that station accepts a place name and the schema confirms partial matching ('Gotthard', 'Muttenz'), shows real road designation formats (A1, A 2, H 18) and canton codes (UR, GR), and explains that sort_by drives ranking. It omits evening_peak from the sort options it lists and says nothing about the limit parameter, whose schema entry has no description at all.

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 specific verb and resource — annual average traffic from FEDRO automatic counting stations — and enumerates the exact metrics returned (vehicles/day, peak hours, day/night averages, heavy-goods share). Scope is unambiguous (filter by station, road or canton; rank nationwide by default). It does not explicitly contrast itself with the sibling get_traffic_counts_nearby, so it falls short of the full sibling-differentiation bar for 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 Guidelines4/5

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

It gives clear operating context: filters can be combined, and 'with no filter it ranks the busiest stations nationwide' defines the default behavior precisely, which is exactly what an agent needs before calling. Three worked examples ({station:'Gotthard'}, {road:'A1', canton:'ZH'}, {sort_by:'heavy_share'}) reinforce usage. It stops short of explicit when-not guidance or naming the nearby-counts sibling as the alternative for spatial queries.

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