Skip to main content
Glama
IBM

Chuk MCP Maritime Archives

by IBM

maritime_wind_rose

Analyze Beaufort wind force and wind direction distributions from historical maritime logbooks, with optional period comparisons to differentiate genuine wind shifts from technological changes.

Instructions

Beaufort wind force and wind direction distributions from CLIWOC logbooks.

Counts observations by Beaufort force (0-12) and compass direction (N, NE, E, SE, S, SW, W, NW) with mean speed at each level. Optionally compares distributions between two periods.

Also includes distance calibration: compares logged distances from ship logbooks against haversine-computed distances from lat/lon positions. Ratio near 1.0 indicates good position accuracy.

Key tool for the Kelly and O Grada approach: if recorded Beaufort distributions shift between periods, that indicates genuine wind change. If distributions are stable while speeds increase, that indicates technology improvement (hull, sails, routing).

Wind direction is available for ~97% of observations. Beaufort force is available for ~17%. Returns has_wind_data/has_direction_data flags. Anchored positions are excluded by default.

Args: lat_min/lat_max/lon_min/lon_max: Bounding box nationality: Filter by nationality code year_start/year_end: Filter by year range direction: Filter by "eastbound" or "westbound" month_start/month_end: Month filter (supports wrap-around) period1_years: First period as "YYYY/YYYY" range or "YYYY,YYYY,..." list period2_years: Second period as "YYYY/YYYY" range or "YYYY,YYYY,..." list 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 Beaufort + direction distribution, calibration, and optional period splits

Tips for LLMs: - Use period1_years/period2_years to compare distributions - Periods accept "YYYY/YYYY" ranges or "YYYY,YYYY,..." year lists - Wind direction available even without Beaufort force data - direction_counts show prevailing wind patterns by compass sector - distance_calibration compares logged vs computed distances - Combine with group_by="beaufort" on aggregate tool for speed profiles at each wind force

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lat_minNo
lat_maxNo
lon_minNo
lon_maxNo
nationalityNo
year_startNo
year_endNo
directionNo
month_startNo
month_endNo
period1_yearsNo
period2_yearsNo
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 comprehensively discloses behavior: it counts observations by Beaufort force and direction, optionally compares periods, includes distance calibration, and notes data availability percentages (97% direction, 17% Beaufort). It also explains the meaning of the ratio and that anchored positions are excluded. With no annotations provided, the description fully carries the behavioral burden.

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 somewhat long but well-structured: overview, Args, Returns, and Tips. Information is front-loaded with the core purpose, and each section adds value. Minor verbosity, but no waste.

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 15 parameters, no output schema, and no annotations, the description covers all parameters, explains return values (JSON or text with distributions and calibration), and provides usage tips. It is complete for the tool's complexity.

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 description coverage is 0%, but the description provides an 'Args' section explaining every parameter in detail, including types, defaults, and special formatting for periods. This adds significant meaning beyond the raw 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 provides Beaufort wind force and wind direction distributions from CLIWOC logbooks, with optional period comparison and distance calibration. It distinguishes itself from related tools like maritime_wind_direction_by_year by its specific focus on distributions and calibration.

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?

Explicit guidance is given for using period1_years/period2_years to compare distributions, and tips for LLMs indicate when to use different features (e.g., wind direction available without Beaufort force). No negative exclusions are provided, but the context is clear.

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