Skip to main content
Glama

get_traffic_by_canton

Read-onlyIdempotent

Retrieve up to 20 ASTRA traffic counting stations for a Swiss canton by canton code to analyze local traffic data.

Instructions

ASTRA traffic counting stations in a canton (max 20)

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": {
      "canton": "<canton>"
    },
    "name": "get_traffic_by_canton"
  }
}

Input Schema

NameRequiredDescriptionDefault
cantonYesCanton code, e.g. ZH

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / canton / description
      Previous value: -"2-letter canton code (e.g. 'ZH', 'BE', 'GE', 'VS')"New value: +"Canton code, e.g. ZH"
  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, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds one genuine behavioral fact — the '(max 20)' result cap, which matters for completeness expectations — but says nothing about what measurements the stations carry or ordering.

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 short sentence with the resource front-loaded and the scope qualifier attached. It wastes nothing, though '(max 20)' is slightly ambiguous about whether it caps returned stations or something else.

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 one-parameter read tool with rich annotations and no output schema, the description covers the essentials of what is retrieved and roughly how much. It leaves the return shape (station identifiers, coordinates, measurement values) unexplained, which an agent would need to know before relying on the output.

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?

Only one parameter, and the schema documents it fully with the same example ('Canton code, e.g. ZH') implied by the description. The description adds no constraint beyond the schema, such as whether the code is case-sensitive or accepts full canton names. Baseline 3 applies given 100% schema coverage.

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 states a specific resource (ASTRA traffic counting stations) and an explicit scope (in a canton), which distinguishes it from siblings like get_traffic_nearby (proximity-based) and get_traffic_count (single-station counts). It stops short of naming those siblings, so the differentiation is inferable from the name rather than stated.

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?

Usage is only implied: an agent can deduce it should call this when it has a canton code and wants a list of counting stations. There is no explicit when-not guidance and no mention of the obvious alternative get_traffic_nearby for location-based lookups.

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