Skip to main content
Glama

MagicON RF Design Engines

by io.github.magiccadai
OverviewDiscussionsAdmin

Design a superheterodyne receiver

design_rf_receiver
Read-only

Design or analyse a superheterodyne RECEIVER. Selects catalog parts for each slot (limiter, LNA, image filter, mixer, LO, IF filter, IF amp, step attenuator) and returns the frequency plan (image, half-IF, LO leakage), the cascaded noise figure, noise floor, MDS, sensitivity, SFDR and dynamic range, plus the ADC interface (sample rate, Nyquist zone, ENOB, jitter limit). Pass rfFrequencyHz to design one; pass stages[] only for a bench receiver the user described with their own numbers. For a transmitter, use design_rf_chain instead. For a module that shares one antenna between transmit and receive, use design_tr_module instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ifHzNoIntermediate frequency in Hz. Omit to let the server choose one and disclose that it did.
loSideNoLO above or below the RF. Omit to let the server pick.
stagesNoExplicit receive chain, ONLY for a bench receiver the user described with their own numbers. Do not hand-build this from memory — pass rfFrequencyHz instead and let the server select real parts.
targetsNoRequirements the user stated, judged pass/fail in the result's validation. Keys: noiseFigure, sensitivity, mds, noiseFloor, imageRejection, sfdr, instantaneousDynamicRange, iip3, rxGain, rxGainMax. Each value is a number or {min, typ, max}. Only values the user gave; never invent one.
applicationNoApplication context, the same label design_rf_chain takes (e.g. drones, marine_radar, wifi_wlan). Every part is scored for it; free text is resolved to the nearest known label, and one that cannot be resolved is scored as 'general' with a warning saying so. Omit for 'general'.
bandwidthHzNoReceiver noise bandwidth in Hz. Required for noise floor, MDS and sensitivity — omit it and those are reported as unavailable rather than assumed.
architectureNofront_end_only for a radio built on an integrated transceiver (drones): selects only limiter, preselector and LNA, ending at the transceiver input. Omit for a full superheterodyne.
user_requestNoThe end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
inputPowerDbmNoSignal level at the antenna port, in dBm. Omit for a small-signal reference, which the result discloses.
requiredSnrDbNoSNR needed at the demodulator, in dB.
rfFrequencyHzNoRF centre frequency in Hz (e.g. 9.4e9 for X-band).
transceiverNfDbNoThe transceiver's own noise figure in dB, front_end_only only. Omit it and system NF, MDS and sensitivity are withheld, never assumed.
main_board_input_voltageNoBoard DC supply voltage in volts, the same argument design_rf_chain takes. This tool returns no bill of materials or power tree, so a value given here is reported back as unused rather than applied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / targets
      Added value: +{
+  "description": "Requirements the user stated, judged pass/fail in the result's validation. Keys: noiseFigure, sensitivity, mds, noiseFloor, imageRejection, sfdr, instantaneousDynamicRange, iip3, rxGain, rxGainMax. Each value is a number or {min, typ, max}. Only values the user gave; never invent one.",
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / user_request / maxLength
      Added value: +4000
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds far more — the full result surface (frequency plan with image/half-IF/LO leakage, cascaded NF, noise floor, MDS, sensitivity, SFDR, ADC interface), plus disclosure behavior when inputs are omitted ('reported as unavailable rather than assumed', 'labelled caller-asserted'). It also warns that a stage built from memory is discouraged and that an omitted nfSideband produces an ambiguity warning, which is genuine behavioral context beyond annotations.

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?

Front-loaded with purpose, then outputs, then parameter routing, then sibling routing — a logical progression with zero filler. Despite being several sentences, each one carries distinct information the agent needs to call the tool correctly.

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

Completeness5/5

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

For a 13-parameter tool with nested stage objects and no output schema, the description compensates by describing the returned quantities in detail and by stating what is withheld when optional inputs are missing. It also flags the no-BOM limitation for main_board_input_voltage, covering the full decision surface.

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 description coverage is 100%, so the baseline is 3. The description adds routing semantics the schema cannot: which of rfFrequencyHz vs stages[] to use and under what user-story condition, plus the note that bandwidthHz gates noise floor/MDS/sensitivity. It stops short of explaining the remaining numeric conventions, which the schema already handles.

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 ('Design or analyse a superheterodyne RECEIVER') and immediately enumerates what it selects (limiter, LNA, image filter, mixer, LO, IF filter, IF amp, step attenuator) and what it returns. It explicitly distinguishes itself from design_rf_chain (transmitter) and design_tr_module (shared antenna), so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit decision rule for the two primary modes ('pass rfFrequencyHz to design one; pass stages[] only for a bench receiver the user described with their own numbers') and names two alternatives with the conditions that select them. No exclusions are left to inference.

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

All MagicON RF Design Engines toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources