Skip to main content
Glama

Traffic counting stations near a point

get_traffic_counts_nearby
Read-only

Find FEDRO traffic counting stations within a chosen radius of a WGS84 coordinate, returned nearest first with exact distances and annual traffic figures.

Instructions

FEDRO counting stations within radius_km of a WGS84 point, nearest first, with exact distances and their annual traffic figures. Example: {lat: 47.05, lon: 8.31, radius_km: 10}.

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

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude
lonYesWGS84 longitude
limitNo
radius_kmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely useful behavior beyond that: result ordering (nearest first) and the fact that each station carries exact distance and annual traffic figures. It stops short of saying how the limit truncates results or what an empty radius returns.

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

Conciseness5/5

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

Two sentences: the capability and its scoping/ordering rules come first, then a compact inline example of all three call-shaping arguments. Nothing is repeated from the schema and nothing is wasted.

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, the description carries the return-value burden and does so partially – it promises exact distances and annual traffic figures plus sort order. The only meaningful omission for a 4-parameter geo tool is the effect of limit on result cardinality.

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 only 50% – lat/lon are documented in the schema, while limit and radius_km have no descriptions there. The description names radius_km and shows it in the example (10 km), which helps, but the limit parameter is never mentioned or explained, so the gap is only partially closed.

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?

States a concrete verb-and-resource: FEDRO counting stations within radius_km of a WGS84 point, with ordering (nearest first) and payload (exact distances, annual traffic figures). It is clearly distinguishable from a generic get_traffic_counts, but it never names a sibling to contrast with.

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?

Proximity search intent is strongly implied by 'within radius_km of a WGS84 point' plus the worked example, so an agent can infer when to reach for it. However, there is no explicit when-to-use/when-not-to-use statement and no pointer to an alternative for fetching figures for a known station.

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