Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_iv_drip_infusion_rate

Calculate electronic IV pump rates in mL/hr and gravity drip rates in gtt/min from prescribed volume, infusion duration, and tubing drip factor to eliminate manual arithmetic errors.

Instructions

IV Drip Rate & Infusion Velocity Calculator. Calculate electronic IV infusion pump rates in mL/hr and gravity drip rates in drops per minute (gtt/min) across macrodrip and microdrip tubing sets. Discipline: BIOTECH. Governing mathematical model / formula: Infusion Rate = Total Volume (mL) / Infusion Time (Hours) | Drip Rate (gtt/min) = [Volume (mL) · Drip Factor] / Time (Minutes).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of pump_rate_ml_hr (Electronic Pump Flow Rate), gravity_drip_rate_gtt_min (Gravity Drip Rate (Drops/Min)), seconds_per_drop (Timing Cadence Per Drop), total_infused_drops (Total Cumulative Drops) using prescribed_iv_volume_ml (Prescribed IV Fluid Volume (mL) in mL), infusion_duration_hours (Infusion Duration (Hours) in hours), iv_tubing_drip_factor (Tubing Drip Factor (gtt/mL) in gtt/mL). 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 'IV Drip Rate & Infusion Velocity 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): "iv-drip-infusion-rate"

    • category (string): "biotech"

    • name (string): "IV Drip Rate & Infusion Velocity Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.pump_rate_ml_hr (Electronic Pump Flow Rate): Formatted display string (e.g. '125.0 mL/hr')

      • metrics.gravity_drip_rate_gtt_min (Gravity Drip Rate (Drops/Min)): Formatted display string (e.g. '31 gtt/min')

      • metrics.seconds_per_drop (Timing Cadence Per Drop): Formatted display string (e.g. '1 Drop Every 1.9 Seconds')

      • metrics.total_infused_drops (Total Cumulative Drops): Formatted display string (e.g. '15,000 Drops')

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

Input Schema

NameRequiredDescriptionDefault
iv_tubing_drip_factorNoTubing Drip Factor (gtt/mL) (gtt/mL). Standard macrodrip is 10, 15, or 20 gtt/mL; pediatric microdrip is 60 gtt/mL. Default: 15. Min: 10. Max: 60.
infusion_duration_hoursNoInfusion Duration (Hours) (hours). Target run time ordered by physician. Default: 8. Min: 0.25. Max: 72.
prescribed_iv_volume_mlNoPrescribed IV Fluid Volume (mL) (mL). Total infusion volume (e.g. 0.9% Normal Saline or D5W). Default: 1000. Min: 10. Max: 5000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.8/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, and free of side effects, and states that out-of-bounds inputs return a diagnostic error status rather than throwing. It also discloses the determinism/precision guarantee, which is the key behavioral trait for trusting the computed numbers.

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?

The structure is strong — labeled sections (usage, disambiguation, behavior, returns) with the purpose front-loaded. There is some redundancy, notably the floating-point precision claim repeated in both the usage and behavior blocks and parameter names restated verbatim from the schema, which costs a bit of tightness on an otherwise disciplined definition.

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?

With no output schema, the description compensates by documenting the full return envelope (status, calculator, category, formula, inputs echo, metrics with four named outputs and sample formatted values). Combined with the formula, bounds behavior, and safety profile, an agent has everything needed to invoke and interpret this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 units, defaults, and min/max bounds for all three parameters; the description's main added value is restating each parameter's clinical meaning alongside the output it feeds, which is useful mapping context. It adds little new syntax or edge-case semantics beyond the schema, so it sits modestly above the baseline rather than far above it.

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 names a specific verb and resource — computing IV pump flow rate in mL/hr and gravity drip rate in gtt/min across macrodrip and microdrip tubing — and states the governing formulas explicitly. It also distinguishes itself from generic dispatchers (omni_universal_query) and from the batch/schema siblings, so an agent can identify it 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?

Explicit WHEN TO USE enumerates the exact outputs (pump_rate_ml_hr, gravity_drip_rate_gtt_min, seconds_per_drop, total_infused_drops) and the exact inputs that drive them, and WHEN NOT TO USE rules out qualitative or non-numeric reasoning. It then routes chained jobs to omni_batch_calculate and schema inspection to omni_describe_solver, giving concrete alternatives rather than leaving inference to the agent.

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