Skip to main content
Glama
IBM

Chuk MCP Maritime Archives

by IBM

maritime_estimate_position

Estimate a ship's position on any date along historical trade routes using linear interpolation between waypoints, aiding wreck location and lost voyage investigation.

Instructions

Estimate a ship's position on a specific date based on its route.

Uses linear interpolation between historical route waypoints to estimate where a ship would have been on a given date, assuming typical sailing times. Works with all 18 routes across VOC, EIC, Carreira, Galleon, and SOIC. Essential for investigating wreck locations and lost voyages.

Args: route_id: Route identifier (from maritime_list_routes or maritime_get_route). See maritime_get_route for full list. departure_date: Ship's departure date as YYYY-MM-DD target_date: Date to estimate position for as YYYY-MM-DD (e.g., last known date, or estimated loss date) use_speed_profiles: If True, enrich estimate with CLIWOC-derived speed statistics for the current route segment (default False) output_mode: Response format — "json" (default) or "text"

Returns: JSON or text with estimated lat/lon, region, route segment, confidence level, and caveats

Tips for LLMs: - Get the departure_date from maritime_get_voyage - Choose route_id based on the voyage's departure/destination ports (use maritime_list_routes to find matching routes) - The estimate is based on TYPICAL sailing times — actual positions varied due to weather, ship condition, and orders - Confidence is "high" at known ports, "moderate" between waypoints, "low" past the expected arrival date - Use maritime_lookup_location on the estimated region for more geographic context - Combine with maritime_assess_position for uncertainty analysis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
route_idYes
departure_dateYes
target_dateYes
use_speed_profilesNo
output_modeNojson
Behavior4/5

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

No annotations provided, but description explains interpolation method, typical sailing times, confidence levels, and limitations (weather, ship condition). Sufficiently transparent.

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?

Well-structured with clear sections: description, Args, Returns, Tips. Every sentence adds value; no filler.

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?

Comprehensive for a tool with no output schema or annotations. Explains return values, confidence levels, and suggests related tools. Covers all necessary information for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description includes an 'Args' section that explains every parameter in detail. Also provides tips for LLMs on how to choose route_id and get departure_date.

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?

Clearly states it estimates a ship's position on a specific date using linear interpolation. Distinguishes from siblings like maritime_assess_position and maritime_get_track.

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?

Provides explicit tips on when to use (investigating wreck locations) and how to get inputs (via maritime_get_voyage, maritime_list_routes). Mentions combining with maritime_assess_position, but does not explicitly state when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IBM/chuk-mcp-maritime-archives'

If you have feedback or need assistance with the MCP directory API, please join our Discord server