AetherLink SDR MCP

Overview Schema Source Related Servers Discussions Admin

pager_find_frequencies

Scans VHF, UHF, and 900 MHz paging bands for narrowband carriers likely to be pager channels, returning strongest candidates first so you can start decoding.

Instructions

Scan the common paging bands (VHF 152-153/157-158 MHz, UHF 454-455/462-463 MHz, 929-932 MHz) for narrowband carriers that are likely pager channels, strongest first. Needs sdr_connect. Follow up with pager_start_decoding on a candidate.

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

Input Schema

Name	Required	Description
`gain`	No	Tuner gain in dB while scanning (restored afterwards)
`bands`	No	Bands to scan; default all three
`min_snr`	No	Minimum SNR in dB for a candidate
`dwell_time`	No	Seconds to listen per step with max-hold (pager bursts are short); 0.2-10
`max_results`	No	Maximum candidates to return

Output Schema

Name	Required	Description	Default
`candidates`	No
`bands_scanned`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

A4/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 burden and does disclose useful behavior: it scans predefined bands, ranks by strength, and the schema notes gain is restored afterwards. However, it doesn't say whether the call blocks, roughly how long a full three-band sweep takes, or that it monopolizes the SDR while running — important for a device-owning operation.

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?

Two tight sentences: capability and scope first, then prerequisite and follow-up. Every clause carries information and nothing is redundant.

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

Completeness4/5

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

An output schema exists so return values need not be explained, and the description covers bands, ranking, prerequisite and next step. The remaining gap is scan duration/blocking behavior and whether a connected SDR is exclusively held during the scan.

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 the baseline is 3. The description does add real meaning by mapping the enum values to actual frequency ranges (VHF 152-153/157-158, UHF 454-455/462-463, 929-932 MHz), which the bare enum lacks, but it adds nothing about gain, min_snr, dwell_time, or max_results beyond the schema.

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?

States a specific verb and resource ('scan the common paging bands ... for narrowband carriers that are likely pager channels') and includes the concrete frequencies scanned plus the 'strongest first' ordering, which clearly distinguishes it from generic siblings like spectrum_scan or ism_start_scanning.

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?

Explicitly states the prerequisite ('Needs sdr_connect') and the natural next step ('Follow up with pager_start_decoding on a candidate'), which is exactly the workflow context an agent needs. It stops short of naming when to prefer this over spectrum_scan, so no explicit alternative/exclusion is given.

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