Skip to main content
Glama

MagicON RF Design Engines

Design a T/R module

design_tr_module
Read-only

Design a T/R (transmit/receive) module that shares ONE antenna between a transmitter and a receiver. Designs both chains through the existing engines, selects the shared front end (a T/R switch, or a circulator with a receive-path limiter), and returns four safety budgets: TX-to-RX isolation against the receiver's damage limit, the receive window left after switching and limiter recovery, limiter leakage driving the LNA into compression, and transmit power against each part's survivability rating. Pass frequencyGhz and targetOutputPowerDbm to design one; pass txPeakPowerDbm and isolationDb only to check a front end the user already described with their own numbers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prfHzNoPulse repetition frequency in Hz, for a pulsed system. Omit and the switching/blanking budget is absent, not assumed.
topologyNoShared-antenna element. Omit to use tr_switch, which the result discloses. Choose circulator_limiter for high transmit power — if the stress budget reports over_limit for a switch, re-run with this. switch_and_circulator belongs to architecture array_element only (and is its only topology); any other pairing is refused.
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.
isolationDbNoTransmit-to-receive isolation in dB, for the explicit-inputs path only.
pulseWidthSNoTransmit pulse width in seconds (e.g. 1e-6).
architectureNofront_end_only for a radio built on an integrated transceiver (drones): selects only limiter, preselector and LNA, ending at the transceiver input. array_element for ONE element of a phased array, beamformer port to antenna port: phase shifter + step attenuator shared by both paths, a low-power T/R switch and a circulator; requires beamformerDriveDbm. Omit for a full superheterodyne.
frequencyGhzNoOperating frequency in GHz (e.g. 9.4 for X-band).
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.
antennaFilterNoarray_element only: true to add a shared bandpass filter between the circulator and the antenna, charged to both paths. Off unless the user asks for it.
requiredSnrDbNoSNR needed at the demodulator, in dB.
beamformerNfDbNoarray_element only: the beamformer's own noise figure behind the common leg, in dB. Omit it and the system noise figure at the beamformer port is withheld.
txPeakPowerDbmNoPeak transmit power AT THE ANTENNA PORT, in dBm. Pass this ONLY to check a front end the user already has — it skips design entirely. To design a module, pass targetOutputPowerDbm instead.
transceiverNfDbNoThe transceiver's own noise figure in dB, front_end_only only. Omit it and system NF, MDS and sensitivity are withheld, never assumed.
beamformerDriveDbmNoarray_element only: the input power at the beamformer port, in dBm, as the user stated it. Required for an array element — never assumed; the tool refuses and names it when absent.
transmitBiasPulsedNoPulsed designs only: true when the user says the transmit amplifier bias (gate or drain) is switched off between pulses, false when it stays on. Omit when not stated — the idle draw between pulses is then counted as heat, and the thermal disclosures say so.
antennaReturnLossDbNoAntenna return loss in dB. Without it the antenna-mismatch leakage path is excluded and disclosed.
targetOutputPowerDbmNoTransmit output power the chain is designed to, in dBm (20 W = 43 dBm). Required — every safety budget is measured against it and no default is substituted.
main_board_input_voltageNoBoard DC supply voltage in volts that the power tree steps down/up to the per-component rails (optional; defaults to 12 V). Set it when the user states their supply rail, e.g. a 14.8 V 4S battery or a 28 V bench input. Same meaning as on design_rf_chain.
transmitDutyCyclePercentNoTransmit duty cycle in percent (e.g. 10 for a 10% pulsed radar). Selects each part's PULSED survivability rating instead of its CW rating, which for a limiter is commonly 7 dB higher. Omit for continuous wave — the CW rating is then used, and a part declaring no pulsed rating keeps its CW one with that substitution disclosed. Redundant if prfHz and pulseWidthS are both given, which imply it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint/openWorldHint, and the description adds real behavioral substance beyond them: the four concrete safety budgets returned, that design runs 'through the existing engines', and the front-end selection logic. Combined with schema-level disclosures of refusals, defaults with 'not assumed' semantics, and withheld values, the agent knows how this behaves.

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 sentences, front-loaded with purpose then invocation routing, with zero filler. The enumerated safety budgets are dense but each carries distinct information.

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 20-parameter tool with no output schema, the description covers the omission: it names the four returned budgets and both invocation modes, and the many defaults/refusals are documented per-parameter in the schema. Only marginal behavioral context (e.g. what the failure/over_limit output looks like) is left unstated, which is acceptable given no output schema.

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 meaning the schema alone does not: the mutually exclusive design vs check parameter pairs and the purpose of each. It doesn't go further into units or validity ranges, which live in 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?

Names a specific verb and resource ('Design a T/R module that shares ONE antenna'), states what it builds (both chains via existing engines), what it selects (T/R switch or circulator + limiter), and what it returns (four named safety budgets). It is clearly distinguishable from design_rf_chain and design_rf_receiver, which it explicitly references for the shared 'application' label.

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?

Routes the agent explicitly: pass frequencyGhz + targetOutputPowerDbm to design, pass txPeakPowerDbm + isolationDb to only check a user-supplied front end. The 'ONLY' qualifier on txPeakPowerDbm and the note that it 'skips design entirely' prevents the wrong invocation path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources