Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_highway_horizontal_curve_radius

Calculates minimum horizontal curve radius and superelevation for highway design using AASHTO inputs, helping engineers verify safe roadway alignment and banking requirements.

Instructions

Roadway Horizontal Alignment Minimum Curve Radius & Superelevation Calculator. Calculate minimum curve radius (R_min in feet), maximum design superelevation banking (e_max %), and side friction factors compliant with AASHTO Green Book. Discipline: ENGINEERING. Governing mathematical model / formula: R_min = V² / [15 · (0.01 · e_max + f_max)] | AASHTO Geometric Design Standard.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of minimum_radius_feet (Minimum Safe Horizontal Radius (R_min)), degree_of_curvature (Maximum Degree of Curve (D_max)), curve_length_feet (Standard Curve Length (for 30° turn)), cross_slope_elevation_diff (Roadway Banking Lift (12-ft Lane)) using highway_design_speed_mph (Design Travel Speed (V in mph) in mph), maximum_superelevation_rate (Maximum Superelevation Rate (e_max %) in %), side_friction_factor (Side Friction Factor (f_max)). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Roadway Horizontal Alignment Minimum Curve Radius & Superelevation Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "highway-horizontal-curve-radius"

    • category (string): "engineering"

    • name (string): "Roadway Horizontal Alignment Minimum Curve Radius & Superelevation Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.minimum_radius_feet (Minimum Safe Horizontal Radius (R_min)): Formatted display string (e.g. '1,480 Feet')

      • metrics.degree_of_curvature (Maximum Degree of Curve (D_max)): Formatted display string (e.g. '3.87° Curvature')

      • metrics.curve_length_feet (Standard Curve Length (for 30° turn)): Formatted display string (e.g. '775 Feet Length')

      • metrics.cross_slope_elevation_diff (Roadway Banking Lift (12-ft Lane)): Formatted display string (e.g. '8.6 Inches Banking Rise')

    • execution_time_ms (number): Latency in milliseconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_highway_horizontal_curve_radius"
  }
}

Input Schema

NameRequiredDescriptionDefault
side_friction_factorNoSide Friction Factor (f_max). AASHTO Green Book comfort factor (0.11 at 65 mph, 0.15 at 40 mph). Default: 0.11. Min: 0.08. Max: 0.18.
highway_design_speed_mphNoDesign Travel Speed (V in mph) (mph). Highway design speed (e.g. 65 mph freeway). Default: 65. Min: 25. Max: 85.
maximum_superelevation_rateNoMaximum Superelevation Rate (e_max %) (%). Standard rural highway: 6% or 8%; Ice/snow regions: 6%. Default: 6. Min: 4. Max: 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full disclosure burden and does so: it states the tool is read-only, idempotent, stateless, with zero side effects, and that out-of-bounds inputs return a safe diagnostic error rather than throwing. It also documents the exact response envelope (status, calculator, category, formula, inputs, metrics, execution_time_ms).

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 purpose and formula, then cleanly sectioned via headers, which is appropriate for a calculation tool with a long return contract. Some content is redundant — the calculator name is restated three times and metric labels repeat their parenthetical descriptions — costing a perfect score.

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?

Although no output schema exists, the RETURNS section fully specifies the JSON envelope and each metric with example formatted values. Combined with validation semantics and domain bounds echoed from the schema, an agent has everything needed to call and interpret results.

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 value by tying each parameter to its role in the formula (V in mph, e_max in %, f_max) and to a named output. It does not add defaults or the comfort-factor rationale, which the schema already supplies, so it stops short of a 5.

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 opening line names a specific verb and resource ('Minimum Curve Radius & Superelevation Calculator') and quotes the governing AASHTO formula R_min = V² / [15 · (0.01 · e_max + f_max)], so an agent knows exactly which computation this performs. It also distinguishes itself from the generic dispatcher omni_universal_query by name.

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?

An explicit WHEN TO USE block enumerates the three inputs and the four derived outputs, and a WHEN NOT TO USE block excludes qualitative/unquantified use. The disambiguation section routes chained jobs to omni_batch_calculate and schema inspection to omni_describe_solver, so both the trigger and the alternatives are stated.

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

Deploy Server

Other Tools