Skip to main content
Glama
IBM

Chuk MCP Maritime Archives

by IBM

maritime_search_cargo

Search historic VOC cargo records for trade goods shipped between Asia and the Netherlands, 1700-1795. Filter by voyage, commodity, origin, or destination.

Instructions

Search for VOC cargo records.

Queries the Boekhouder-Generaal Batavia (BGB) cargo database for trade goods shipped between Asia and the Netherlands, 1700-1795. All search parameters are optional and combined with AND logic. Supports cursor-based pagination.

Args: voyage_id: Filter by specific voyage commodity: Commodity name or partial name (e.g., pepper, cloves, textiles, silver, porcelain) origin: Origin port or region destination: Destination port or region date_range: Date range as "YYYY/YYYY" or "YYYY-MM-DD/YYYY-MM-DD" min_value: Minimum cargo value in guilders archive: Restrict to a specific archive (default: voc_cargo) max_results: Maximum results per page (default: 100, 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 cargo records and pagination metadata

Tips for LLMs: - Use commodity to search for specific trade goods - Use voyage_id to see all cargo on a specific voyage; alternatively use maritime_get_cargo_manifest for the full list - Common VOC commodities: pepper, cloves, nutmeg, mace, cinnamon, textiles, porcelain, silver, copper, tea, coffee, sugar - Values are in contemporary Dutch guilders - If has_more is true, pass next_cursor as cursor to get the next page - Combine with maritime_search_voyages to find the voyage context

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
voyage_idNo
commodityNo
originNo
destinationNo
date_rangeNo
min_valueNo
archiveNo
max_resultsNo
cursorNo
output_modeNojson
Behavior4/5

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

Despite no annotations, the description discloses key behavioral traits: all parameters optional, AND logic, cursor-based pagination, response format options, default and max values. Lacks mention of auth or rate limits, but search tool context mitigates.

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 is informative, no redundancy. Efficiently packed with necessary details.

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?

Covers all 10 parameters, pagination, response format, example commodities, and cross-references sibling tool. No missing context given lack of output schema.

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 schema has 0% description coverage, but the description's Args section adds rich meaning: date_range format, min_value unit (guilders), archive default, cursor usage, output_mode options. Fully compensates for lack of schema descriptions.

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 'Search for VOC cargo records' and specifies the database (BGB) and time period (1700-1795). It distinguishes from sibling maritime_get_cargo_manifest by noting that alternative should be used for a full list on a specific voyage.

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?

Provides explicit tips for LLMs, including when to use each parameter, combination with maritime_search_voyages, and when to use an alternative tool (maritime_get_cargo_manifest). Also notes that all parameters are optional and combined with AND logic.

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