Skip to main content
Glama

get_traffic_nearby

Read-onlyIdempotent

Find ASTRA traffic counting stations near a WGS84 coordinate within a chosen radius to identify local traffic data sources.

Instructions

ASTRA traffic counting stations near a WGS84 point

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "get_traffic_nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude (WGS84)
lonYesLongitude (WGS84)
radiusNoMetres

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.0
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude in WGS84 (e.g. 47.3769 for Zürich)"New value: +"Latitude (WGS84)"
    • changedInput schema / properties / lon / description
      Previous value: -"Longitude in WGS84 (e.g. 8.5417 for Zürich)"New value: +"Longitude (WGS84)"
    • addedInput schema / properties / radius / default
      Added value: +5000
    • changedInput schema / properties / radius / description
      Previous value: -"Search radius in meters (default: 5000)"New value: +"Metres"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false. The description adds domain context that it retrieves ASTRA traffic counting stations by proximity, but it does not disclose return format, result limits, or record contents. It provides some context beyond annotations without contradicting them.

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 phrase with no filler. It is a sentence fragment and lacks a title, so it is slightly less polished than a full-sentence definition.

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

Completeness3/5

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

For a simple three-parameter read-only lookup, the description identifies the data and spatial query. With no output schema, it does not say what the response contains or how many stations may be returned, leaving a modest gap.

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 description coverage is 100%, and the schema documents lat, lon and radius (metres, default 5000). The description adds no parameter detail beyond 'WGS84 point', so the baseline 3 applies.

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 the verb (get) and resource (ASTRA traffic counting stations) and specifies the spatial scope (near a WGS84 point). It does not explicitly name competing siblings such as get_traffic_by_canton, so it is clear but not maximally differentiated.

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?

The phrase 'near a WGS84 point' implies this is the proximity-search variant, but there is no explicit when-to-use guidance, no naming of alternatives like get_traffic_by_canton or get_traffic_count, and no exclusions.

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