Skip to main content
Glama

İETT hat bilgileri ve tarifesi

istanbul_transit_line
Read-onlyIdempotent

Get IETT line info, ordered stops or planned main-terminal departures.

limit applies only to departures. This is not live intermediate-stop ETA.
Cross-operator service notices are provided by istanbul_transport_disruptions.

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": {
      "line_code": "<line_code>"
    },
    "name": "istanbul_transit_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
actionNoinfo
line_codeYes

Output Schema

NameRequiredDescriptionDefault
okNo
dataNo
errorNo
limitsNo
geojsonNo
sourcesNo
summaryYes
warningsNo
freshnessYes
paginationNo
result_infoNo
next_queriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / $defs / ResultInfo / properties / coverage
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "maxProperties": 20,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Coverage"
      +}
    • addedOutput schema / $defs / ResultInfo / properties / empty_reasons
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "maxItems": 30,
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Empty Reasons"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / $defs / ResultInfo / properties / filter_counts
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {
      +        "type": "integer"
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Filter Counts"
      +}
  3. Changed2 schema fields changed
    • addedOutput schema / $defs / Source / properties / refresh_status
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "idle",
      +        "refreshing",
      +        "failed",
      +        "unavailable"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Refresh Status"
      +}
    • addedOutput schema / $defs / Source / properties / serving_stale
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Serving Stale"
      +}
  4. Changed1 schema field changed
    • addedOutput schema / $defs / Source / properties / url / description
      Added value: +"Human-readable source page for citations; null when the source is only an API endpoint or data file."
  5. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real value by signalling the data is planned/scheduled rather than live, and that limit is scoped to departures only. It does not mention rate limits, paging, or what happens when a line code is unknown, so beyond-annotation disclosure is useful but thin.

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?

Three short sentences, capability stated first, then the limit constraint, then the exclusion and the sibling hand-off. No sentence is filler and nothing is buried mid-paragraph.

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?

An output schema exists, so return shapes need not be described. For a 3-parameter read tool the description covers the main ambiguities (live vs planned, limit scope, disruptions elsewhere); only line_code formatting and action-selection guidance are left uncovered.

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 0%, so the description must carry parameter meaning; it clarifies the scoping of limit (departures only), which is genuinely helpful. However, line_code is required and its expected format (e.g. '34B', operator prefix) is never described, and the action modes are only implied rather than defined.

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?

Uses a concrete verb plus resource ("Get IETT line info") and enumerates the three modes — info, ordered stops, planned main-terminal departures — which map cleanly to the action enum. It distinguishes itself from istanbul_transport_disruptions for service notices, but does not name istanbul_next_departures, which is the nearest confusing sibling given the departures mode.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit negative guidance is given: "This is not live intermediate-stop ETA" and cross-operator notices belong to istanbul_transport_disruptions. What is missing is guidance on when to choose action=stops versus action=departures, and when istanbul_next_departures is the better call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.