Skip to main content
Glama
IBM

Chuk MCP Maritime Archives

by IBM

maritime_search_tracks

Search historical ship tracks from the CLIWOC database (1662-1855) by nationality, date range, geographic bounding box, or ship name.

Instructions

Search historical ship tracks from the CLIWOC database (1662-1855).

Returns voyage track summaries from ~261K daily logbook observations recorded by 8 European maritime nations. Each track represents one voyage with dated lat/lon positions from the ship's logbook. Supports cursor-based pagination and geographic bounding box filtering.

Args: nationality: Two-letter nationality code to filter by. Options: NL (Dutch), UK (British), ES (Spanish), FR (French), SE (Swedish), US (American), DE (German), DK (Danish) year_start: Earliest year to include (e.g., 1700) year_end: Latest year to include (e.g., 1750) ship_name: Ship name or partial name (case-insensitive; requires CLIWOC 2.1 Full data) lat_min: Minimum latitude — track must have at least one position in the bounding box (e.g., -50 for Roaring Forties south bound) lat_max: Maximum latitude (e.g., -30 for Roaring Forties north bound) lon_min: Minimum longitude (e.g., 15 for Indian Ocean west bound) lon_max: Maximum longitude (e.g., 110 for Indian Ocean east bound) max_results: Maximum results per page (default: 50, max: 500) cursor: Pagination cursor from a previous result's next_cursor field output_mode: Response format - "json" (default) or "text"

Returns: JSON or text with matching track summaries and pagination metadata

Tips for LLMs: - Use nationality filter to find ships of a specific nation - Combine year_start/year_end to narrow to a specific period - Use lat_min/lat_max/lon_min/lon_max to find tracks passing through a geographic region (e.g., lat_min=-50, lat_max=-30 for Roaring Forties) - Results show track summaries (start/end dates, position count) - If has_more is true, pass next_cursor as cursor to get the next page - Follow up with maritime_get_track to get full position data - Use maritime_nearby_tracks to find ships near a wreck site - CLIWOC covers 1662-1855 with most data from 1750-1850 - Nationality breakdown: UK (732), NL (677), ES (472), FR (85)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nationalityNo
year_startNo
year_endNo
ship_nameNo
lat_minNo
lat_maxNo
lon_minNo
lon_maxNo
max_resultsNo
cursorNo
output_modeNojson
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses cursor-based pagination, has_more/next_cursor fields, and that ship_name requires CLIWOC 2.1 Full data. It clearly indicates it is a read-only search operation. However, it does not mention authentication or rate limits, though these may not be applicable.

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 long but well-structured with clear sections (summary, Args, Returns, Tips). It is front-loaded with the essential purpose. Some redundancy exists (e.g., the period is mentioned twice), but overall it is efficient and well-organized.

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 the complexity (11 parameters, no output schema), the description is complete. It covers all parameters, pagination, return format, and provides tips on using filters and combining with other tools. It also clarifies data scope and limitations (CLIWOC period, nationality counts).

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 input schema has 0% description coverage, so the description fully compensates. It explains each parameter in detail, including nationality options, bounding box meaning (track must have at least one position in box), and pagination mechanics. This adds significant meaning beyond the bare schema.

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 it searches historical ship tracks from the CLIWOC database (1662-1855), a specific verb and resource. It distinguishes from siblings by mentioning alternatives like maritime_get_track for full position data and maritime_nearby_tracks for nearby ships.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool (searching tracks with filters) and when to use alternatives (e.g., 'Follow up with maritime_get_track to get full position data' and 'Use maritime_nearby_tracks to find ships near a wreck site'). It also includes tips for effective 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