Skip to main content
Glama
IBM

Chuk MCP Maritime Archives

by IBM

maritime_track_tortuosity

Compute route tortuosity by comparing actual sailed distance to great-circle distance, revealing how directly a historical voyage progressed. Use to analyze navigation efficiency and detours.

Instructions

Compute route tortuosity for a single CLIWOC voyage.

Tortuosity = path_km / net_km. A value of 1.0 means perfectly direct; higher values indicate meandering. Compares actual sailed distance (sum of position-to-position haversine legs) to great-circle distance (first to last position in bbox).

Args: voyage_id: CLIWOC voyage ID (from maritime_search_tracks) lat_min: Minimum latitude for bounding box lat_max: Maximum latitude for bounding box lon_min: Minimum longitude for bounding box lon_max: Maximum longitude for bounding box min_speed_km_day: Minimum speed filter (default: 5.0) max_speed_km_day: Maximum speed filter (default: 400.0) output_mode: Response format - "json" (default) or "text"

Returns: JSON or text with path_km, net_km, tortuosity_r, inferred_direction, n_in_box

Tips for LLMs: - Use lat_min=-50, lat_max=-30 for the Roaring Forties - Tortuosity ~1.0-1.1 = direct sailing, >1.3 = detours - Compare pre/post-chronometer voyages to test navigation - Use maritime_aggregate_track_tortuosity for bulk analysis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
voyage_idYes
lat_minNo
lat_maxNo
lon_minNo
lon_maxNo
min_speed_km_dayNo
max_speed_km_dayNo
output_modeNojson
Behavior5/5

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

The description fully explains the behavioral traits: it computes tortuosity using a specific formula, compares distances, and returns specific fields (path_km, net_km, etc.). No annotations are provided, but the description carries the burden transparently.

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?

The description is well-structured with sections for overview, formula, args, returns, and tips. It is slightly verbose but front-loaded with the core purpose, making it easy to parse.

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?

Given 8 parameters, no output schema, and no annotations, the description is exceptionally complete: it explains the formula, return values, and provides practical tips for usage, leaving no significant gaps.

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?

The description includes an 'Args' section that documents all 8 parameters, adding context such as practical lat/lon ranges and default speed values, which goes beyond the schema alone. The schema coverage is effectively 100% in the description despite the indicator.

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?

The description clearly states 'Compute route tortuosity for a single CLIWOC voyage.' using a specific verb and resource, and distinguishes from the sibling tool 'maritime_aggregate_track_tortuosity' for bulk analysis.

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?

The description provides explicit tips for LLMs on when to use specific lat/lon ranges and how to interpret tortuosity values, and mentions using 'maritime_aggregate_track_tortuosity' for bulk analysis, offering good alternative guidance.

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