Skip to main content
Glama
İzmir Açık Veri MCP
by batuoncel

Hattaki otobüslerin anlık konumu

otobus_konumlari

Fetches live latitude and longitude positions for all buses on a specified ESHOT line, helping users track vehicles and count unique buses by direction.

Instructions

Bir ESHOT otobüs hattındaki (ör. 35, 202) tüm otobüslerin canlı konumunu (enlem/boylam) getirir. 'yon' alanı ESHOT'un yön kodudur (0 veya 1) ve otobüsün hattın iki yönünden hangisinde gittiğini gösterir; hangi kodun hangi uca gittiği henüz doğrulanmadı, bu yüzden kullanıcıya yön adı söyleme, sadece aynı yönde giden otobüsleri grupla. Aynı otobusId birden fazla konum kaydında görünebilir; otobüs sayısı olarak benzersiz otobusId sayısını kullan.

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": {
      "hatNo": "<hatNo>"
    },
    "name": "otobus_konumlari"
  }
}

Input Schema

NameRequiredDescriptionDefault
hatNoYesESHOT hat numarası, ör. 35

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does real work: it discloses that the 'yon' code's mapping is unverified, that the same otobusId can appear in multiple records, and that results are live coordinates. It stops short of stating error behavior for an unknown hatNo or whether an empty result is possible.

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?

Three tight sentences, front-loaded with what is returned, then the two data quirks an agent would otherwise get wrong. No filler, though the yon-handling sentence is more output-processing advice than tool definition.

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

Completeness5/5

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

With no output schema and no annotations, the description still tells the agent what fields come back (lat/lon, yon, otobusId) and how to interpret them, including the duplicate-ID caveat. Nothing an agent needs in order to call and use the result correctly is missing.

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 single parameter is already documented with the same 'ör. 35' example, so the description adds almost nothing new about hatNo beyond a second example (202). Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb and resource ('getirir' + 'tüm otobüslerin canlı konumunu') scoped to an ESHOT line, and gives concrete line examples (35, 202). An agent can immediately tell this returns live bus positions rather than schedules or route geometry.

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?

Gives handling guidance after retrieval (do not name the direction, group buses by the same 'yon', count unique otobusId) but never states when this tool should be chosen over anything else or what preconditions apply. With no meaningful sibling to compare against, usage is only implied.

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