Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP

turkey_greek_islands_ferry_schedules

Turkey & Greek Islands Ferry Schedules: Real-time structured data extraction feed for Turkey & Greek Islands Ferry Schedules.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  3. First observed

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it discloses only that data is 'real-time' and 'structured.' It says nothing about rate limits, authentication, geographic or operator coverage, freshness guarantees, or whether results are scraped live versus cached.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the resource name, but the second clause is redundant filler that repeats the title and conveys almost no new information. Nothing is wasted in length, but little is earned.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description should clarify what a returned item contains (routes, departure times, prices, operators). That gap leaves the agent unable to predict the response shape or judge whether the tool fits a query.

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?

There is a single optional parameter (maxResults) with 100% schema description coverage, so the schema already explains it fully. The description adds no meaning beyond that, which meets the baseline of 3 for high schema coverage.

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

Purpose2/5

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

The description restates the tool name almost verbatim ("Turkey & Greek Islands Ferry Schedules" twice) and only adds the vague phrase "real-time structured data extraction feed." An agent learns it is a data-feed tool about ferries, but not what it actually returns or how it differs from siblings like turkey_bus_routes_prices.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as other Turkey travel-data tools. The only implied usage is 'if you want ferry schedule data,' which the name already conveys.

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.