Skip to main content
Glama
IBM

Chuk MCP Maritime Archives

by IBM
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

maritime_search_crew

Search historical crew muster rolls from VOC and Dutch archives by name, rank, ship, voyage, origin, fate, or date range to find individual crew records.

Instructions

Search for crew members in muster roll records.

Queries crew databases across multiple archives. By default queries the VOC Opvarenden database (774,200 personnel records, 1633-1794). Set archive="dss" to query MDB individual crew records from northern Dutch provinces (77,043 records, 1803-1837).

Args: name: Crew member name or partial name (case-insensitive) rank: Rank or role (e.g., schipper, stuurman, matroos, soldaat) ship_name: Ship name or partial name voyage_id: Specific voyage identifier to list all crew origin: Place of origin or partial name date_range: Date range as "YYYY/YYYY" or "YYYY-MM-DD/YYYY-MM-DD" fate: Crew fate - survived, died_voyage, died_asia, deserted, discharged (VOC Opvarenden only) archive: Archive to search - "voc_crew" (default, 1633-1794) or "dss" (MDB northern provinces, 1803-1837) 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 crew records and pagination metadata

Tips for LLMs: - Use voyage_id to list the complete crew of a specific voyage - Set fate="died_voyage" to find crew lost at sea (VOC only) - Names are in historical Dutch spelling; try partial matches - If has_more is true, pass next_cursor as cursor to get the next page - Follow up with maritime_get_crew_member for full details including pay and embarkation date - Set archive="dss" for post-VOC era crew from Groningen, Friesland, Drenthe, Overijssel (1803-1837) - Combine with maritime_search_voyages to cross-reference ship and voyage information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
rankNo
ship_nameNo
voyage_idNo
originNo
date_rangeNo
fateNo
archiveNo
max_resultsNo
cursorNo
output_modeNojson

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

With no annotations, description fully carries disclosure. It reveals querying multiple archives, default vs. alternate, pagination with cursor, output modes, and historical spelling. Lacks details on rate limits or authentication, but covers core behavior well.

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?

Description is long but well-structured with Args and Tips sections. Main purpose and usage are front-loaded. Some redundancy in Tips (e.g., archive again), but overall efficient given parameter count.

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?

For a tool with 11 parameters, no annotations, and no output schema, the description is comprehensive. Covers pagination, output formats, cross-referencing with other tools, and historical context, making it fully actionable for an AI agent.

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 has 0% coverage, so description adds all meaning. Args section explains each of 11 parameters, including allowed values for fate, archive, max_results default, and cursor usage. This fully compensates for missing 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?

Clearly states 'Search for crew members' verb+resource. Additionally contrasts with sibling maritime_get_crew_member for follow-up, and lists many sibling tools that are distinct, so no confusion with other search tools.

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 when-to-use for each parameter (e.g., voyage_id for full crew, fate filter for survival analysis), archive selection by era, and tips for LLMs on pagination and cross-references. Implicitly warns against using without filters via default behavior (VOC archive).

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