Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_compression_ratio

Calculate engine static compression ratio from cylinder swept volume, chamber, gasket, and piston volumes to get deterministic results and eliminate LLM arithmetic errors.

Instructions

Engine Static Compression Ratio Calculator. Calculate static compression ratio (CR) from cylinder swept volume, combustion chamber cc, head gasket thickness/bore, and piston dome/dish volume. Discipline: PHYSICS. Governing mathematical model / formula: Compression Ratio = (Swept Volume + Clearance Volume) / Clearance Volume.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of static_cr_result (Static Compression Ratio), total_clearance_vol (Total Clearance Volume), octane_guidance (Recommended Fuel Octane), total_cylinder_volume (Total BDC Volume) using cyl_swept_vol_cc (Cylinder Swept Volume (cc) in cc), chamber_cc (Cylinder Head Chamber Volume (cc) in cc), gasket_cc (Compressed Head Gasket Volume (cc) in cc), piston_net_cc (Piston Dome (+) or Dish/Deck (-) Volume (cc) in cc). 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 'Engine Static Compression Ratio 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): "compression-ratio"

    • category (string): "physics"

    • name (string): "Engine Static Compression Ratio Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.static_cr_result (Static Compression Ratio): Formatted display string (e.g. '9.27 : 1.0')

      • metrics.total_clearance_vol (Total Clearance Volume): Formatted display string (e.g. '60.50 cc')

      • metrics.octane_guidance (Recommended Fuel Octane): Formatted display string (e.g. 'Regular 87 AKI Unleaded')

      • metrics.total_cylinder_volume (Total BDC Volume): Formatted display string (e.g. '560.50 cc')

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

Input Schema

NameRequiredDescriptionDefault
gasket_ccNoCompressed Head Gasket Volume (cc) (cc). Volume occupied by head gasket bore/thickness. Default: 6.5. Min: 1. Max: 25.
chamber_ccNoCylinder Head Chamber Volume (cc) (cc). Measured combustion chamber volume. Default: 58. Min: 20. Max: 150.
piston_net_ccNoPiston Dome (+) or Dish/Deck (-) Volume (cc) (cc). Dish adds volume (-); dome reduces clearance (+). Default: -4. Min: -50. Max: 50.
cyl_swept_vol_ccNoCylinder Swept Volume (cc) (cc). Single cylinder displacement in cc. Default: 500. Min: 50. Max: 2000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/5.0
Behavior4/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 well: it declares read-only, idempotent, stateless behavior with zero side effects, and explains that out-of-bounds inputs return a safe diagnostic error rather than throwing. The only gap is that it does not state the exact physical bounds or what a validation error payload looks like, though the schema covers the bounds.

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-loads purpose, then formula, then usage, then behavior, then returns – a clean hierarchy. It is somewhat long and the RETURNS block is verbose, but since no output schema exists that detail is largely justified rather than padding.

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?

No output schema exists, and the description compensates by documenting every returned field including the metrics sub-keys and their display formats. Combined with the formula, validation behavior, and defaults echo, an agent has everything needed to call and interpret this tool.

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 all four parameters already carry units, defaults, and min/max in the schema. The description restates the parameter names and units but adds no new semantics such as the sign convention rationale or interaction between chamber and gasket volume, 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?

States a specific verb and resource ('Calculate static compression ratio (CR)') and enumerates the exact inputs that drive it (swept volume, chamber cc, gasket thickness/bore, piston dome/dish). The governing formula is spelled out, so an agent knows precisely what computation this performs and can distinguish it from the many other ratio calculators in the sibling list.

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 explicit WHEN TO USE with the named outputs and inputs, an explicit WHEN NOT TO USE clause excluding qualitative reasoning and non-numeric inputs, and SIBLING ROUTING that names omni_universal_query as the generic alternative and points to it for cross-discipline dispatch. This is the full when/when-not/alternative triad.

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