Skip to main content
Glama

İstanbul trafik endeksi

istanbul_get_traffic_index

Retrieve İBB's live Istanbul traffic congestion index (0–100) overall and by Asian and European sides to assess current road conditions.

Instructions

Live Istanbul traffic congestion index 0–100 (trafik yoğunluğu) overall and for the Asian (Anadolu) and European (Avrupa) sides, from İBB.

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": "istanbul_get_traffic_index"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose useful behavior: the data is live, the index range is 0–100, and results are split into overall, Anadolu, and Avrupa. It says nothing about refresh cadence, caching, or failure modes, which is a real gap for a live-data tool.

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?

A single front-loaded sentence that names the deliverable, its scale, its breakdown, and its provenance. No filler, no redundancy, nothing left dangling.

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?

For a zero-parameter read of a live index with no output schema, the description tells the agent what it will get (a 0–100 congestion value plus per-side breakdowns). Only the exact response shape and freshness/staleness behavior are left implicit, which is minor here.

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?

Zero parameters, so there is nothing to document and the schema cannot be improved upon. Baseline of 4 applies; no parameter meaning is missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (Istanbul traffic congestion index) with a concrete scale (0–100), granularity (overall plus Asian/European sides), and data source (İBB). It is unmistakable against the listed siblings, none of which touch traffic, so no sibling differentiation is needed.

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 word 'Live' implies this is the current-snapshot tool, so usage is reasonably inferable. There is no explicit when-to-use framing, no statement about whether historical or forecast traffic exists, and no alternatives offered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.