Skip to main content
Glama
Sign In

Gangway AIS

by com.gangwayais
OverviewDiscussionsAdmin

Plan a passage

plan_route
Read-onlyIdempotent

A sea route between two positions, through the traffic separation schemes, with its distance and legs. Give the vessel's length and draught to keep her in water deep enough. A planning aid from charts and data that can be wrong: never for navigation. At most 6 a minute. Credits: 10. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

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": {
      "from_lat": "<from_lat>",
      "from_lon": "<from_lon>",
      "to_lat": "<to_lat>",
      "to_lon": "<to_lon>"
    },
    "name": "plan_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_latYesLatitude in decimal degrees, north positive
to_lonYesLongitude in decimal degrees, east positive
from_latYesLatitude in decimal degrees, north positive
from_lonYesLongitude in decimal degrees, east positive
length_mNoHer length overall in metres
draught_mNoHer draught in metres

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: a rate limit of 6 per minute, a cost of 10 credits, a paid-plan requirement, and an accuracy caveat that the charts and data can be wrong. The annotations already cover read-only, open-world, idempotent, and non-destructive behavior; the description adds operational and reliability context.

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?

Front-loads what the tool returns, then explains the key optional parameters, the safety caveat, and operational limits. The sentence fragments are terse but every clause carries information; the phrasing could be slightly smoother but is not padded.

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?

Covers purpose, the rationale for key optional parameters, a safety caveat, rate/cost/plan constraints, and hints at output ('distance and legs'). Without an output schema the exact return structure is not fully specified, but the definition is sufficient for correct invocation.

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 schema already documents all six parameters. The description adds meaning by explaining why length and draught matter: they keep the vessel in water deep enough, which affects routing beyond the schema's unit definitions.

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?

States a specific resource and scope: a sea route between two positions via traffic separation schemes, returning distance and legs. It is clear what the tool produces, though it does not explicitly distinguish itself from sibling check_route.

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?

Provides a clear when-not warning ('never for navigation') and frames the tool as a planning aid. However, it gives no explicit guidance on when to choose it over check_route or other route-related siblings.

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

All Gangway AIS toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources