Skip to main content
Glama

MagicON RF Design Engines

by io.github.magiccadai
OverviewDiscussionsAdmin

Run a link budget

run_link_budget
Read-only

Compute a cascaded RF link budget. For the chain just designed, call with NO arguments — the server derives stages and input power from the design. Pass stages + inputPowerDbm only for a bench/hypothetical chain. Returns per-stage output power, cumulative gain, Friis cascaded NF, gain-referred reciprocal-sum cascaded OIP3, P1dB headroom warnings, and overall risk. Optionally pass bandwidthHz (and requiredSnrDb) to also get the receiver noise floor, MDS, sensitivity, SFDR, and instantaneous dynamic range. For a link through the air between two antennas (EIRP, path loss, range), use run_ota_link instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stagesNoOrdered list of RF stages for a bench/hypothetical chain. Omit for a just-designed chain (derived server-side). Each stage may declare gainDB or lossDB (loss is treated as -|lossDB|), nfDB, oip3Dbm, p1dbDbm, and an authoritative outputPowerDbm that snap-seeds the cascade. Mark a mixer with mixerRole, plus nfSideband when the user or datasheet says which definition its nfDB uses.
bandwidthHzNoOptional receiver noise bandwidth in Hz. When given, the result adds the thermal noise floor, MDS, SFDR, and instantaneous dynamic range (a receiver figure of merit).
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.
inputPowerDbmNoInput power into the first stage, in dBm. Omit for a just-designed chain (derived from its power flow).
requiredSnrDbNoOptional SNR (dB) required for detection/demod. With bandwidthHz, yields receiver sensitivity = MDS + this SNR.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_request / maxLength
      Added value: +4000
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only establish readOnlyHint/openWorldHint; the description goes well beyond by disclosing that stages and input power are derived server-side for the no-arg case, that omitting user_request labels results 'caller-asserted', and that outputs include headroom warnings and an ambiguity warning for mixers. This is rich behavioral context an agent could not infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and the no-arg rule, then progressively optional modes, then the sibling escape hatch. Dense and useful throughout, though the mid-sentence return-value list makes it a long single block rather than cleanly segmented.

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?

No output schema exists, so the description correctly enumerates return figures (per-stage power, cascaded NF/OIP3, headroom warnings, noise floor/MDS/SFDR), covers the optional branches, and points to the sibling for the air-link case. Nothing needed to invoke it correctly is missing.

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 baseline is 3, but the description adds genuine meaning: the conditional pairing of bandwidthHz with requiredSnrDb, the semantics of the zero-argument mode, and the stages/inputPowerDbm coupling. It stops short of explaining every nested stage field, which the schema already handles well.

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?

Opens with a specific verb+resource ('Compute a cascaded RF link budget') and immediately distinguishes itself from the sibling run_ota_link by scope (on-board chain vs over-the-air link). An agent can route between the two without opening either 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 explicit branch conditions: call with NO arguments for a just-designed chain, pass stages + inputPowerDbm only for a bench/hypothetical chain, and use run_ota_link for air links. When-to-use, when-not-to-use, and the named alternative are all present.

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