Skip to main content
Glama
Sign In
Chuk MCP Maritime Archives

Chuk MCP Maritime Archives

by IBM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

maritime_capabilities

Retrieve complete server capabilities including archives, tools, ship types, and geographic regions. Use this to plan your maritime research workflow.

Instructions

List full server capabilities: archives, tools, and reference data.

Returns a comprehensive overview of this maritime archives server including all available archives, registered tools, supported ship types, and geographic regions. Call this first to understand what the server can do.

Args: output_mode: Response format - "json" (default) or "text"

Returns: JSON or text with server capabilities

Tips for LLMs: - Call this FIRST to plan a research workflow - The archives list shows available data sources and their coverage periods - The tools list shows every registered tool with its category and description - ship_types lists valid values for vessel type filters - regions lists valid values for geographic region filters - Typical workflow: maritime_capabilities -> maritime_search_voyages or maritime_search_wrecks -> detail tools -> export/analysis

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_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
output_modeNojson

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

A4.9/5.0
Behavior5/5

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

Discloses the comprehensive nature of the response, including archives, tools, ship types, and regions. Explains that output can be JSON or text based on the output_mode parameter. No annotations exist, so description carries full burden; it does so thoroughly.

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 sections (title, description, args, returns, tips). Each sentence adds value, and important information is front-loaded. No unnecessary repetition.

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?

As a capability-listing tool, the description covers what it returns, how to use it, and its role in a workflow. No output schema exists, but the description adequately details the output structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, output_mode, has a default but no enum in schema. The description adds valid values ('json' or 'text') and explains its effect, which compensates for the 0% schema coverage.

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 that the tool lists full server capabilities (archives, tools, reference data) and instructs to 'Call this first to understand what the server can do.' This distinguishes it from sibling tools that perform searches or retrieve specific records.

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?

Explicitly advises to call this first for workflow planning, provides a typical workflow sequence, and explains the contents of each section of the output. This gives clear when-to-use and how-to-use guidance.

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

Deploy Server

Other Tools