Skip to main content
Glama

Durağa yaklaşan otobüsler

get_stop_arrivals
Read-onlyIdempotent

Fetch approaching ESHOT buses and estimated arrival minutes for an İzmir bus stop by stop number or name, including multiple platforms sharing the same name.

Instructions

Bir ESHOT otobüs durağına yaklaşan otobüsleri ve tahmini varış süresini (dakika) verir. stop durak numarası (ör. '40010') ya da durak adı olabilir (ör. 'Bornova Metro', 'Konak İskele'). Aynı adlı birden çok peron varsa hepsine bakar. Süreler kalan durak sayısı ve otobüs konumundan tahmindir.

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": {
      "stop": "<stop>"
    },
    "name": "get_stop_arrivals"
  }
}

Input Schema

NameRequiredDescriptionDefault
stopYesDurak numarası veya durak adı
limitNoEn fazla kaç otobüs listelensin

Output Schema

NameRequiredDescriptionDefault
metaYes
errorNo
queryYes
stopsNo
arrivalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds genuine behavioral context beyond that: all platforms sharing a name are queried, and arrival times are derived estimates from remaining stops and bus position rather than live promises.

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?

Four short sentences with the core purpose front-loaded, followed by input forms and the estimation caveat. Slightly redundant between the opening mention of 'tahmini varış süresi' and the closing note that times are estimates, but nothing is wasted.

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?

An output schema exists, so return values need not be explained. With two fully documented parameters, the multi-platform behavior and the estimation model disclosed, an agent has everything needed to call this correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by showing concrete examples of stop identifiers ('40010', 'Bornova Metro', 'Konak İskele') and explaining that a name may match multiple platforms. The limit parameter is left to the schema, which documents it adequately.

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?

The description names a specific verb and resource: it returns buses approaching a given ESHOT stop along with estimated arrival times in minutes. Scope details (number vs. name, multi-platform, estimate basis) make it unambiguous and impossible to confuse with the unrelated sibling find_pharmacies.

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 implied by the description — use it to see what is arriving at a stop — and the accepted input forms are spelled out with examples. There is no explicit when-not guidance or alternative tool to route to, since the only sibling serves a different domain.

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