AetherLink SDR MCP

Overview Schema Source Related Servers Discussions Admin

marine_track_vessels

Track ships via AIS on both marine channels using the built-in SDR receiver—no extra software—until stopped or a set duration; requires a coastal or waterway location.

Instructions

Start tracking ships via AIS (161.975 and 162.025 MHz, both channels) with the built-in receiver (no extra software). Runs until marine_stop_tracking or the duration ends. Needs a coastal or waterway location.

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": "marine_track_vessels"
  }
}

Input Schema

Name	Required	Description	Default
`gain`	No	RTL-SDR tuner gain in dB
`engine`	No	Receiver: built-in (default) or external AIS-catcher / rtl_ais	auto
`duration`	No	Tracking duration in seconds; 0 runs until stopped

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the frequencies, dual-channel reception, the 'built-in receiver, no extra software' default, and the termination conditions. It leaves out whether a device must be connected first, what happens if no receiver is available, and how data is surfaced afterward, which are material for a long-running capture.

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?

Three short sentences with the action front-loaded and the precondition last; every sentence carries information. The parenthetical frequency and 'no extra software' asides are mildly decorative but still relevant to SDR users.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter start-tracking tool with no annotations and no output schema, the definition covers purpose, prerequisite, and stop conditions adequately. It is still silent on the prerequisite hardware state and on how to retrieve captured vessels, which are the two things an agent most needs next.

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

Parameters3/5

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

Schema description coverage is 100%, so gain, engine, and duration are already documented in structured form. The description only echoes the duration-termination behavior and the built-in receiver default; it adds no syntax or tuning guidance beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ('Start tracking ships via AIS') plus the concrete bands used, and it names marine_stop_tracking as the terminating counterpart, so the agent can place it among the marine_* and aviation_* tracking siblings without opening the schema.

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?

It gives the key precondition ('Needs a coastal or waterway location') and the lifecycle rule (runs until marine_stop_tracking or the duration ends), which tells the agent when this is appropriate. It stops short of explicitly routing the agent to marine_get_vessels for results or stating that an SDR must already be connected, so no full when/when-not pairing.

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