Skip to main content
Glama

İzmir vapur saatleri

izmir_get_ferry_times

Fetches İzdeniz ferry departure schedules for a specified İzmir pier (e.g., Konak, Karşıyaka) for today or a given date to help plan travel.

Instructions

İzdeniz ferry departures from a pier in İzmir (vapur saatleri: Konak, Karşıyaka, Bostanlı, Alsancak, Üçkuyular…) for today or a given date.

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": {
      "iskele": "<iskele>"
    },
    "name": "izmir_get_ferry_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
tarihNoTarih (YYYY-MM-DD). Boşsa bugün.
iskeleYesİskele, ör. "Karşıyaka", "Konak"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the default-date behavior ('today or a given date'), but says nothing about the return shape (departure list), timezone, ordering, how 'limit' truncates results, or what happens when the pier name is unrecognized or misspelled.

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 front-loaded sentence with the resource and scope stated first and the pier examples in a compact parenthetical. No filler, though the examples could arguably move into the 'iskele' schema field where an agent would look for them.

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 three-parameter, no-annotation, no-output-schema lookup tool, the description covers the core intent but leaves the 'limit' parameter and the shape of the returned departure list entirely undocumented. An agent can call it, but cannot predict result volume or failure modes.

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 67%, with 'limit' undocumented anywhere. The description compensates by expanding the pier vocabulary well beyond the schema's two examples (adding Bostanlı, Alsancak, Üçkuyular), which matters because 'iskele' is a free-form string with no enum. It restates the date default rather than adding to it, and leaves 'limit' unexplained.

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 names a specific resource and action ('İzdeniz ferry departures from a pier in İzmir') and lists concrete pier examples (Konak, Karşıyaka, Bostanlı, Alsancak, Üçkuyular), so an agent can tell this apart from the rail sibling izmir_get_izban_times. It is clear and concrete, though it never explicitly contrasts itself with that sibling.

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 by the resource: call this to get ferry departure times for a pier, for today or a supplied date. There is no explicit when-to-use statement, no when-not-to-use, and no mention of the rail alternative for cross-water vs. land travel decisions.

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