Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_projectile_motion

Calculate ballistic trajectory range, maximum height, flight time, and impact velocity from launch velocity, angle, and initial height to avoid arithmetic and formula mistakes.

Instructions

Projectile Motion & Ballistic Trajectory Calculator. Calculate ballistic flight trajectory, maximum apogee height, total hang time, and horizontal ground range under gravitational acceleration. Discipline: PHYSICS. Governing mathematical model / formula: Range R = [v₀² · sin(2θ)] / g | Max Height H = [v₀² · sin²(θ)] / (2g).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of max_range (Total Horizontal Range), max_height (Maximum Altitude (Apogee)), flight_time (Total Hang Time), impact_velocity (Terminal Impact Velocity) using velocity_v0 (Initial Launch Velocity (v₀) in m/s), launch_angle (Launch Angle (θ) in degrees), initial_height (Initial Release Height (y₀) in meters). 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 'Projectile Motion & Ballistic Trajectory 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): "projectile-motion"

    • category (string): "physics"

    • name (string): "Projectile Motion & Ballistic Trajectory Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.max_range (Total Horizontal Range): Formatted display string (e.g. '206.42 meters')

      • metrics.max_height (Maximum Altitude (Apogee)): Formatted display string (e.g. '51.61 meters')

      • metrics.flight_time (Total Hang Time): Formatted display string (e.g. '6.49 seconds')

      • metrics.impact_velocity (Terminal Impact Velocity): Formatted display string (e.g. '45.00 m/s (162.0 km/h)')

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

Input Schema

NameRequiredDescriptionDefault
velocity_v0NoInitial Launch Velocity (v₀) (m/s). Muzzle or launch velocity in meters per second. Default: 45. Min: 1. Max: 5000.
launch_angleNoLaunch Angle (θ) (degrees). Angle above horizontal (45° maximizes range in vacuum). Default: 45. Min: 1. Max: 89.
initial_heightNoInitial Release Height (y₀) (meters). Elevation of launch platform above ground. Default: 0. Min: 0. Max: 1000.

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?

No annotations exist, so the description carries the full burden and does so: it declares pure deterministic computation with machine floating-point precision, read-only/idempotent/stateless semantics with zero side effects, and explicitly describes input validation behavior — out-of-bounds arguments return a diagnostic error status rather than throwing. It even documents the error/success status field.

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?

Sectioned and front-loaded (purpose, usage, behavior, returns), so an agent can scan quickly. Some redundancy exists — the tool name, category, and formula are restated across the purpose, formula, and RETURNS blocks — and the per-metric example strings are verbose, but the length is defensible given there is no output schema.

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 stateless 3-parameter calculator with no output schema, the definition covers everything needed: parameter semantics via schema, validation and error semantics, statelessness, and a field-by-field description of the returned JSON with example values. Nothing material is missing for correct invocation or interpretation of results.

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 units, defaults, and min/max for velocity_v0, launch_angle, and initial_height are already fully specified in the schema. The description restates the parameter names and units in its WHEN TO USE line, which is mild reinforcement rather than new meaning; the baseline of 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 ballistic flight trajectory, maximum apogee height, total hang time, and horizontal ground range' — and lists the exact metrics produced. It also names the governing formulas, so an agent can distinguish this physics calculator from unrelated 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?

Contains explicit WHEN TO USE (deterministic computation of max_range, max_height, flight_time, impact_velocity), WHEN NOT TO USE (qualitative reasoning, non-numeric inputs), and SIBLING ROUTING that names omni_universal_query as the generic dispatcher and states when to prefer it. 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