Skip to main content
Glama

get_traffic_count

Read-onlyIdempotent

Retrieve ASTRA traffic counting station volumes by location name, such as Gotthard, to check Swiss road traffic counts.

Instructions

ASTRA traffic counting station volumes by location name

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "location": "<location>"
    },
    "name": "get_traffic_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYese.g. Gotthard

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / location / description
      Previous value: -"Station or location name to search (e.g. 'Gotthard', 'Zürich', 'Basel')"New value: +"e.g. Gotthard"
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. Beyond that the description adds nothing an agent could not guess: no mention of what a 'volume' means (hourly? daily? averaged?), how current the data is, or what happens when a location match is ambiguous.

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

Conciseness3/5

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

One short phrase with no wasted words and a clear head noun, but it is a label rather than a description; the brevity comes at the cost of any operational detail.

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?

For a one-parameter read tool with full annotations this could be adequate, but there is no output schema, so the description should say what comes back (measurement periods, units, station identifiers matched). It also leaves the sibling-routing question entirely unanswered in a crowded traffic/transport namespace.

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% and the single parameter already carries an example ('Gotthard'). The description's 'by location name' confirms the filter is a name rather than an ID, which is mildly useful, but no additional syntax, casing, or matching rules are given.

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 phrase 'ASTRA traffic counting station volumes by location name' names the source (ASTRA), the resource (counting-station traffic volumes) and the filter (location name), so an agent knows roughly what it retrieves. It stops short of distinguishing itself from close siblings such as get_traffic_by_canton or get_traffic_nearby, which also return traffic data.

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 pick this tool over get_traffic_by_canton, get_traffic_nearby, or get_station_passengers. The only implicit signal is 'by location name', which the agent must infer as the selection criterion.

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