Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_prestressed_concrete_elongation

Calculate theoretical post-tension tendon elongation, jacking force, and curvature wobble friction losses to verify prestressed concrete strand acceptance tolerances.

Instructions

Pre-Stressed Concrete Post-Tension Tendon Elongation & Friction Loss Calculator. Calculate theoretical tendon elongation (ΔL in inches), jack jacking force, and curvature wobble friction losses (PTI / ACI 318 standards). Discipline: ENGINEERING. Governing mathematical model / formula: Tendon Elongation ΔL = (P_avg · L) / (A_ps · E_ps) | Friction Loss P_x = P_0 · e^-(μα + Kx).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of theoretical_elongation_inches (Theoretical Tendon Elongation), allowable_tolerance_range (Job-Site Acceptance Tolerance (±7%)), friction_wobble_loss_kips (Friction & Wobble Force Loss), average_prestress_force_kips (Effective Average Tendon Force) using tendon_length_feet (Total Tendon Length (Feet) in ft), number_of_strands (Number of 0.5-inch 7-Wire Strands in strands), initial_jacking_force_kips (Total Initial Jacking Force (kips) in kips (33.3 kips/strand)). 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 'Pre-Stressed Concrete Post-Tension Tendon Elongation & Friction Loss 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): "prestressed-concrete-elongation"

    • category (string): "engineering"

    • name (string): "Pre-Stressed Concrete Post-Tension Tendon Elongation & Friction Loss Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.theoretical_elongation_inches (Theoretical Tendon Elongation): Formatted display string (e.g. '9.18 Inches')

      • metrics.allowable_tolerance_range (Job-Site Acceptance Tolerance (±7%)): Formatted display string (e.g. '8.54" to 9.82" Range')

      • metrics.friction_wobble_loss_kips (Friction & Wobble Force Loss): Formatted display string (e.g. '14.2 Kips Lost to Friction')

      • metrics.average_prestress_force_kips (Effective Average Tendon Force): Formatted display string (e.g. '126.1 Kips')

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

Input Schema

NameRequiredDescriptionDefault
number_of_strandsNoNumber of 0.5-inch 7-Wire Strands (strands). Standard unbonded monostrand or bonded multi-strand tendon. Default: 4. Min: 1. Max: 27.
tendon_length_feetNoTotal Tendon Length (Feet) (ft). Length between jacking anchorages. Default: 120. Min: 20. Max: 400.
initial_jacking_force_kipsNoTotal Initial Jacking Force (kips) (kips (33.3 kips/strand)). 80% of ultimate 270 ksi tensile strength. Default: 133.2. Min: 20. Max: 1000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and it does so well: pure deterministic computation, read-only/idempotent/stateless, zero side effects, and out-of-bounds inputs returning a diagnostic error instead of throwing. It stops short of stating whether defaults are silently applied vs. required, and the 'machine floating-point precision' claim is asserted without noting numerical limits.

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?

The description is front-loaded and sectioned into usage, boundaries, behavior, and returns, which helps scanning. However it is bloated: the calculator name and the full parameter list with units are repeated across sections, and priced phrases like 'Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes' are marketing rather than operational guidance.

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?

With no output schema and no annotations, this definition does the needed work: it enumerates the returned JSON keys and metric fields with example formatting, plus error status semantics. The only gap is that defaults are never described as auto-applied in the description, requiring the agent to consult 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 coverage is 100% and the schema already documents all three parameters with defaults, min/max, and units, so the description's restatement of them in WHEN TO USE adds little. The one genuine addition is domain context (33.3 kips/strand, ±7% acceptance tolerance, 80% of ultimate 270 ksi), but it is not tied explicitly to how parameters should be set. 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?

The description states a specific verb-and-resource ('Calculate theoretical tendon elongation... jacking force, and curvature wobble friction losses') and scopes it to ENGINEERING with the governing formulas shown. It explicitly says to use this specialist tool rather than omni_universal_query, so an agent can distinguish it from siblings without opening the 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?

There is an explicit WHEN TO USE listing each computed output and its inputs, a WHEN NOT TO USE clause excluding qualitative/unquantified reasoning, and disambiguation routing multi-calculation jobs to omni_batch_calculate and schema inspection to omni_describe_solver. Nothing about selection 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