AetherLink SDR MCP

Overview Schema Source Related Servers Discussions Admin

sdr_set_ppm

Set RTL-SDR frequency correction in parts per million using a measured or known reference value to reduce tuning offset.

Instructions

Set the RTL-SDR frequency correction in parts per million (from rtl_test -p or a known reference)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ppm": "<ppm>"
    },
    "name": "sdr_set_ppm"
  }
}

Input Schema

Name	Required	Description	Default
`ppm`	Yes	Correction in PPM

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden. It does not say whether the correction applies immediately, whether it persists across reconnects or process restarts, or whether a device must be connected first — all relevant for a device-mutating setter.

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 sentence, front-loaded with the verb and target, with the qualifier placed immediately after. Nothing is wasted and nothing important is buried.

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 single-parameter tool with a fully documented schema, this is close to adequate, but the absence of any statement about device-connection requirements or persistence of the setting leaves a real behavioral gap for a mutation operation.

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% (baseline 3), and the description goes beyond the schema's 'Correction in PPM' by explaining where the value comes from (rtl_test -p or a known reference), which meaningfully guides the agent in producing a sensible input.

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 ('Set the RTL-SDR frequency correction') and names the unit, which distinguishes it from sibling tuning tools like sdr_set_frequency and sdr_set_gain. It does not explicitly name those siblings, but the resource noun makes the distinction inferable.

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?

The parenthetical 'from rtl_test -p or a known reference' implies when this is appropriate (after measuring error), but there is no explicit when-to-use/when-not guidance and no mention of prerequisites such as an active connection.

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