Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_thermal_expansion_bridge_joints

Calculate bridge thermal movement and size expansion joint seals under AASHTO LRFD from expansion length, material, and design temperatures, returning recommended joint type and installation gap.

Instructions

Bridge Superstructure Thermal Expansion & Expansion Joint Sizing Calculator. Calculate total thermal movement (expansion and contraction ΔL in inches) and select bridge expansion joint seals (strip seal, modular joint) under AASHTO LRFD. Discipline: ENGINEERING. Governing mathematical model / formula: Thermal Movement ΔL = α · L · ΔT | Steel α = 6.5 × 10⁻⁶ /°F, Concrete α = 6.0 × 10⁻⁶ /°F.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of total_thermal_movement_in (Total Thermal Movement Range (ΔL)), recommended_joint_type (Recommended Expansion Joint), effective_temperature_range (Design Temperature Range (ΔT)), installation_gap_at_60f (Target Setting Gap @ 60°F) using bridge_expansion_length_ft (Bridge Continuous Expansion Length (Feet) in ft), superstructure_material (Superstructure Material (1 = Structural Steel, 2 = Prestressed Concrete)), max_design_temp_f (Maximum Design Summer Temperature (°F) in °F), min_design_temp_f (Minimum Design Winter Temperature (°F) in °F). 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 'Bridge Superstructure Thermal Expansion & Expansion Joint Sizing 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): "thermal-expansion-bridge-joints"

    • category (string): "engineering"

    • name (string): "Bridge Superstructure Thermal Expansion & Expansion Joint Sizing Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.total_thermal_movement_in (Total Thermal Movement Range (ΔL)): Formatted display string (e.g. '3.28 Inches')

      • metrics.recommended_joint_type (Recommended Expansion Joint): Formatted display string (e.g. 'Strip Seal Joint (Up to 4.0" movement)')

      • metrics.effective_temperature_range (Design Temperature Range (ΔT)): Formatted display string (e.g. '120.0°F Range')

      • metrics.installation_gap_at_60f (Target Setting Gap @ 60°F): Formatted display string (e.g. '1.91 Inches Setting Gap')

    • 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_thermal_expansion_bridge_joints"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_design_temp_fNoMaximum Design Summer Temperature (°F) (°F). AASHTO maximum bridge deck temperature. Default: 110. Min: 85. Max: 130.
min_design_temp_fNoMinimum Design Winter Temperature (°F) (°F). AASHTO minimum bridge deck temperature. Default: -10. Min: -40. Max: 30.
superstructure_materialNoSuperstructure Material (1 = Structural Steel, 2 = Prestressed Concrete). 1: Steel (α = 0.0000065/°F), 2: Concrete (α = 0.0000060/°F). Default: 1. Min: 1. Max: 2.
bridge_expansion_length_ftNoBridge Continuous Expansion Length (Feet) (ft). Distance from fixed bearing to expansion joint. Default: 350. Min: 25. Max: 2500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.5/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 burden and does so: it declares the tool read-only, idempotent, stateless with zero side effects, deterministic with machine floating-point precision, and specifies that out-of-bounds inputs return a diagnostic error status rather than throwing. It also documents the full return payload, including the metrics keys and their formatted-string nature.

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

Conciseness3/5

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

Well front-loaded with purpose, formula, and guidance sections, but the WHEN TO USE sentence is bloated with redundant restatements of every parameter name, label, and unit already present in the schema (e.g. 'bridge_expansion_length_ft (Bridge Continuous Expansion Length (Feet) in ft)'). The RETURNS block is long but justified since no output schema exists.

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 deterministic four-parameter calculator with no annotations and no output schema, the description supplies everything needed: formula, input bounds behavior, error semantics, side-effect profile, and an explicit enumeration of the returned fields and their formats. An agent could call and interpret this tool without opening the schema.

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 description coverage is 100%, so the schema already documents every parameter, including units, defaults, ranges, and the material enum mapping. The description restates those same parameter names, units, and coefficients in the WHEN TO USE line without adding new semantics, so the baseline 3 applies.

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 (thermal expansion calculation and expansion-joint sizing) and states the governing model with material coefficients (ΔL = α·L·ΔT, steel 6.5e-6/°F, concrete 6.0e-6/°F). That is clearly distinguishable from the bridge-adjacent siblings (omni_bridge_loan_interest, omni_cross_chain_bridge_fee) and from the other engineering solvers.

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?

Provides an explicit WHEN TO USE list, an explicit WHEN NOT TO USE exclusion (qualitative or unquantified reasoning, non-numeric inputs), and named alternatives for related jobs (omni_universal_query for generic dispatch, omni_batch_calculate for chained jobs, omni_describe_solver for schema inspection). Nothing is left to inference.

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