calc.engineer

lora param optimizer

lora_param_optimizer

Recommends optimal LoRa spreading factor, bandwidth, and TX power based on target range, terrain, and optimization priority. Iterates through all SF (7-12) and BW (125/250/500 kHz) combinations, computing achievable range, airtime, data rate, and battery impact for each. Ranks candidates by priority: 'range' maximizes distance, 'speed' minimizes airtime, 'battery' minimizes power consumption, 'balanced' penalizes extremes. Respects regional TX power limits (FCC/ETSI/ACMA) and duty cycle constraints. Returns the recommended parameters with estimated range, airtime, duty-cycle message limit, battery life, and data rate. Essential for tuning Meshtastic and LoRa deployments to specific requirements.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`region`	No	Regulatory region. Determines max TX power and duty cycle limit.	US915
`terrain`	No	Terrain type for path loss model. open: line-of-sight, suburban: light buildings, urban: moderate buildings, dense_urban: city center, indoor: inside buildings.	suburban
`priority`	No	Optimization priority. range: maximize distance (high SF, low BW). speed: minimize airtime (low SF, high BW). battery: minimize power draw. balanced: best trade-off across all factors.	balanced
`target_range_km`	Yes	Desired communication range in kilometers.
`antenna_gain_dbi`	No	Antenna gain in dBi. 2.15 = half-wave dipole reference.
`max_payload_bytes`	No	Maximum payload size in bytes for airtime calculation.

Output Schema

TableJSON Schema

Name	Required	Description
`airtime_ms`	Yes	Packet airtime in milliseconds for the given payload.
`data_rate_bps`	Yes	Effective data rate in bits per second.
`recommended_sf`	Yes	Recommended spreading factor (7-12).
`estimated_range_km`	Yes	Estimated achievable range in km with the recommended parameters.
`recommended_bw_khz`	Yes	Recommended bandwidth in kHz (125, 250, or 500).
`recommended_tx_dbm`	Yes	Recommended transmit power in dBm.
`estimated_battery_hours`	Yes	Estimated battery life in hours with a 3000 mAh reference battery.
`messages_per_hour_limit`	Yes	Maximum messages per hour under regional duty cycle constraint.

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description fully carries the burden. It discloses iterative search over all SF/BW combos, respect for regional TX power limits and duty cycle, and ranking by priority. No contradictions.

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?

The description is a single paragraph of ~100 words, dense with information. It front-loads the main purpose and is efficient, though could be slightly more structured with bullet points.

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?

Given the tool's complexity (6 params, 3 enums), the description covers optimization logic, constraints, and outputs. An output schema exists (though not shown), so return values need not be detailed. Complete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds process context (iteration, ranking) but not additional per-parameter details beyond what the schema already provides with enums and defaults.

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?

The description clearly states the tool 'Recommends optimal LoRa spreading factor, bandwidth, and TX power' and distinguishes it from sibling tools like lora_airtime and lora_range_estimate by specifying its iterative optimization over SF/BW combinations.

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

Usage Guidelines4/5

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

The description implies usage context with 'Essential for tuning Meshtastic and LoRa deployments' but does not explicitly state when not to use or compare to alternatives like lora_range_estimate. It does mention the optimization priorities, aiding selection.

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

All calc.engineer tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Despite 89 tools, each has a clearly distinct purpose with detailed descriptions that often reference related tools. Overlap exists (e.g., multiple LoRa/RF tools), but the descriptions are sufficient to distinguish them. Some confusion possible among similar-sounding tools like attenuator_pi and attenuator_tee, but the descriptions explicitly compare them.

Naming Consistency4/5

Consistent underscore-separated lowercase naming. Most tools follow a verb_noun pattern (e.g., capacitor_charge, wire_gauge) or noun_noun (power_cost). Minor inconsistencies such as 'bmi_calculator' vs 'solar_sizing' but overall predictable.

Tool Count2/5

89 tools is far too many for a single MCP server. This scope is more appropriate for multiple specialized servers. The sheer number will slow agent selection and increase cognitive load, reducing coherence.

Completeness3/5

Covers many domains (RF, solar, PCB, networking, math, etc.) but lacks depth in some areas (e.g., no three-phase power, no airflow calculations). Some domains have comprehensive coverage (LoRa/Meshtastic), but others feel incomplete for the tool count.

Resources

Need Help?