Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_truss_method_of_joints

Calculate internal axial tension and compression forces in pin-jointed Pratt and Warren truss members from applied loads and truss geometry using static equilibrium.

Instructions

Truss Member Axial Tension & Compression (Method of Joints) Calculator. Calculate internal axial forces (tension or compression in kips) in pin-jointed Pratt and Warren truss members using static equilibrium. Discipline: ENGINEERING. Governing mathematical model / formula: Σ F_x = 0 | Σ F_y = 0 | T_member = P / (2 · sin(θ)).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of diagonal_member_force_kips (Diagonal Web Member Force), top_chord_compression_kips (Top Chord Axial Compression), end_reaction_force_kips (End Support Vertical Reaction), web_angle_degrees (Diagonal Web Member Angle) using vertical_node_load_kips (Point Load at Center Joint (P in Kips) in kips), truss_panel_span_ft (Truss Panel Length (Feet) in ft), truss_depth_height_ft (Truss Overall Height (Feet) in ft). 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.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Truss Member Axial Tension & Compression (Method of Joints) Calculator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

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): "truss-method-of-joints"

    • category (string): "engineering"

    • name (string): "Truss Member Axial Tension & Compression (Method of Joints) Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.diagonal_member_force_kips (Diagonal Web Member Force): Formatted display string (e.g. '20.0 Kips (Tension)')

      • metrics.top_chord_compression_kips (Top Chord Axial Compression): Formatted display string (e.g. '16.0 Kips (Compression)')

      • metrics.end_reaction_force_kips (End Support Vertical Reaction): Formatted display string (e.g. '12.0 Kips Upward')

      • metrics.web_angle_degrees (Diagonal Web Member Angle): Formatted display string (e.g. '36.9° Slope Angle')

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

Input Schema

NameRequiredDescriptionDefault
truss_panel_span_ftNoTruss Panel Length (Feet) (ft). Horizontal distance between joints. Default: 10. Min: 3. Max: 40.
truss_depth_height_ftNoTruss Overall Height (Feet) (ft). Vertical height between top and bottom chords. Default: 7.5. Min: 2. Max: 30.
vertical_node_load_kipsNoPoint Load at Center Joint (P in Kips) (kips). Concentrated load applied at middle bottom chord node. Default: 24. Min: 2. Max: 250.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/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 states that out-of-bounds inputs return a safe diagnostic error rather than throwing. It also discloses the exact response envelope, which compensates for the missing output schema.

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 purpose and formula, then cleanly sectioned into usage, behavior, and returns. It is somewhat verbose, repeating parameter names and units already in the schema, but the structural headings keep it scannable and the returns section earns its length.

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 description fully enumerates the return object including status, echoed inputs, and every metric field with example formatted values. For a three-parameter deterministic calculator with documented validation behavior, an agent has everything needed to call and interpret it.

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% and each parameter already carries units, defaults, and min/max in the schema. The description restates the same parameter names, units, and defaults in the usage section without adding physical interpretation such as how span and depth jointly determine the web angle. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

States a specific verb and resource: calculates internal axial tension/compression forces in pin-jointed Pratt and Warren truss members via the method of joints, naming the governing equilibrium equations. It is clearly distinguishable from the generic sibling dispatcher omni_universal_query.

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 section enumerating the computed quantities and the exact inputs, an explicit WHEN NOT TO USE section (no qualitative or unquantified reasoning, all inputs numeric), and sibling routing away from omni_universal_query. Nothing about tool 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