Skip to main content
Glama
Sign In
AetherLink SDR MCP

AetherLink SDR MCP

by N-Erickson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pager_start_decoding

Start decoding POCSAG pager messages with a built-in decoder, optionally filtering by baud rate and stopping by duration or command. Monitor common paging frequencies without extra software.

Instructions

Start decoding POCSAG pager messages with the built-in decoder (no extra software; 512/1200/2400 baud at once). Runs until pager_stop_decoding or the duration ends. Common paging frequencies: 152-153 MHz, 454 MHz, 929-931 MHz; pager_find_frequencies can locate active channels.

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

Input Schema

NameRequiredDescriptionDefault
gainNoRTL-SDR gain in dB
engineNoDecoder engine: built-in (default) or external rtl_fm + multimon-ngauto
durationNoDecoding duration in seconds; 0 runs until stopped
baud_rateNoDecode only this POCSAG baud rate; omit to decode all three
frequencyNoPager frequency in Hz (e.g., 152240000). Defaults to the connected SDR's current frequency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/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. It discloses useful behavior such as using the built-in decoder, decoding all three baud rates at once, and terminating via stop or duration, but it omits whether the call blocks, whether it holds exclusive SDR access, and how decoded messages are later retrieved.

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?

The description is three compact sentences with no wasted wording. It front-loads the core action, then adds termination behavior and frequency guidance in a logical order.

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?

The description covers the core start action, termination behavior, and frequency discovery, but for a long-running decoder with no annotations and no output schema it omits important context such as SDR prerequisites and the need to retrieve messages via pager_get_messages. It is adequate but leaves meaningful operational gaps.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds practical meaning beyond the schema by naming common paging frequency bands and clarifying that the built-in decoder needs no extra software. It still does not add parameter-specific detail for gain or duration beyond what the schema already provides.

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 uses a specific verb and resource: 'Start decoding POCSAG pager messages.' It also distinguishes the action from pager_stop_decoding and pager_find_frequencies, so an agent can identify the tool's role 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?

The description explains that decoding runs until pager_stop_decoding or the duration ends, and it points to pager_find_frequencies for locating active channels. It provides clear context but does not explicitly state prerequisites such as connecting an SDR first.

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