Chuk MCP Maritime Archives

Overview Schema Source Related Servers Discussions Admin

maritime_export_geojson

Export historical shipwreck positions as GeoJSON FeatureCollection for mapping and spatial analysis. Filter by region, wreck IDs, or status.

Instructions

Export wreck positions as a GeoJSON FeatureCollection.

Creates a GeoJSON document with Point features for each wreck site. Can export specific wrecks by ID or all wrecks matching filter criteria. Suitable for mapping and GIS analysis.

Args: wreck_ids: Specific wreck IDs to export (overrides other filters) region: Region filter. Options: north_sea, atlantic_europe, atlantic_crossing, cape, mozambique_channel, indian_ocean, malabar, coromandel, ceylon, bengal, malacca, indonesia, south_china_sea, japan, caribbean status: Wreck status filter - found, unfound, approximate archive: Restrict to a specific archive include_uncertainty: Include position uncertainty radius in properties (default: true) include_voyage_data: Include ship type, tonnage, loss cause, lives lost, and depth in properties (default: true) output_mode: Response format - "json" (default) or "text"

Returns: JSON with GeoJSON FeatureCollection and feature count

Tips for LLMs: - Provide wreck_ids for a targeted export of specific sites - Use region and status filters for geographic or discovery status based exports - The GeoJSON uses WGS84 coordinates (EPSG:4326) - Include_uncertainty adds uncertainty_km to each feature's properties (useful for drawing search area buffers) - Include_voyage_data enriches features with vessel and loss context (useful for thematic mapping) - Use the output for mapping, spatial analysis, or as input to drift modelling tools

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "maritime_export_geojson"
  }
}

Input Schema

Name	Required	Default
`wreck_ids`	No
`region`	No
`status`	No
`archive`	No
`include_uncertainty`	No
`include_voyage_data`	No
`output_mode`	No	json

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.11May 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Given no annotations, the description carries full burden. It discloses that it creates a GeoJSON document with WGS84 coordinates, explains properties added by booleans, and notes output formats. It does not mention potential errors, rate limits, or performance implications, but for a read-only export tool, it provides sufficient behavioral 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?

The description is well-structured with sections, but includes a 'Tips for LLMs' section that partly repeats information from the Args. It is fairly concise for the level of detail, earning a slightly above-average score.

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?

Despite having 7 parameters and no output schema, the description covers all parameter functionality, explains the return format (GeoJSON FeatureCollection with count), and provides usage context. It is comprehensive enough for an agent to use the tool effectively.

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?

With schema description coverage at 0%, the description fully compensates by explaining each parameter's purpose and options (e.g., region list, status options, default values for booleans, output_mode choices). This adds significant meaning beyond the bare JSON 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 exports wreck positions as a GeoJSON FeatureCollection. This distinguishes it from sibling tools like search_wrecks (list/search) and get_wreck (single wreck details), as it specifically creates a GIS-ready format.

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 on using specific parameters (wreck_ids, region, status) and explains the benefits of include_uncertainty and include_voyage_data. However, it does not explicitly contrast with alternative tools like maritime_search_wrecks or maritime_get_wreck, leaving some ambiguity for when to use this export tool vs. other data retrieval methods.

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

Deploy Server