AetherLink SDR MCP

by N-Erickson

Overview Schema Source Related Servers Discussions Admin

Python

Local

pager_stop_decoding

Stops POCSAG pager decoding and returns the SDR to Python control so you can resume other signal analysis tasks.

Instructions

Stop decoding POCSAG pager messages and return the radio to Python control

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

A3.7/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 usefully discloses the key effect — the radio is released back to Python control — but says nothing about whether buffered/decoded messages are preserved or lost, whether pager_get_messages should be called first, or what happens if no decoding session is running.

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?

A single front-loaded sentence with no filler. The action and its consequence are both conveyed in one pass.

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?

For a trivial zero-parameter stop tool with no output schema, the description covers the action and the state change that matters. It falls just short of full completeness by omitting any note about message buffering or the no-op case.

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 tool takes zero parameters, so there is nothing for the description to clarify; the schema is empty and complete. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Stop decoding POCSAG pager messages") plus the side effect of returning the radio to Python control, which clearly distinguishes it from pager_start_decoding and pager_get_messages. It does not explicitly name the sibling it complements, but the name/description pairing leaves no ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: call this when finished decoding pager traffic. There is no explicit statement about when the tool should not be used, whether it is safe to call when decoding is not active, or how it relates to alternatives like sdr_disconnect or satellite_stop_decoding.

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