Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_mean_arterial_pressure

Calculate Mean Arterial Pressure and organ perfusion adequacy from systolic and diastolic readings using a deterministic formula for exact, validated clinical results.

Instructions

Mean Arterial Pressure (MAP) Calculator. Calculate Mean Arterial Pressure (MAP) and organ perfusion adequacy from systolic and diastolic blood pressure readings. Discipline: HEALTH. Governing mathematical model / formula: MAP = Diastolic BP + [1/3 × (Systolic BP - Diastolic BP)].

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of map_value (Mean Arterial Pressure), pulse_pressure (Pulse Pressure (SBP - DBP)), perfusion_status (Organ Perfusion Adequacy), cardiac_cycle_split (Cardiac Cycle Weighting) using systolic_bp (Systolic Blood Pressure (SBP) in mmHg), diastolic_bp (Diastolic Blood Pressure (DBP) in mmHg). 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 'Mean Arterial Pressure (MAP) 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): "mean-arterial-pressure"

    • category (string): "health"

    • name (string): "Mean Arterial Pressure (MAP) Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.map_value (Mean Arterial Pressure): Formatted display string (e.g. '93.3 mmHg')

      • metrics.pulse_pressure (Pulse Pressure (SBP - DBP)): Formatted display string (e.g. '40.0 mmHg')

      • metrics.perfusion_status (Organ Perfusion Adequacy): Formatted display string (e.g. 'Optimal Perfusion (70 - 105 mmHg)')

      • metrics.cardiac_cycle_split (Cardiac Cycle Weighting): Formatted display string (e.g. '67% Diastole / 33% Systole')

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

Input Schema

NameRequiredDescriptionDefault
systolic_bpNoSystolic Blood Pressure (SBP) (mmHg). Top number (peak ventricular contraction). Default: 120. Min: 60. Max: 240.
diastolic_bpNoDiastolic Blood Pressure (DBP) (mmHg). Bottom number (ventricular relaxation). Default: 80. Min: 40. Max: 140.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.5/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 disclosure burden and does so: pure deterministic computation, read-only/idempotent/stateless, zero side effects, and validation that returns a diagnostic error status rather than throwing. Combined with the detailed RETURNS block, an agent knows both the safety profile and the failure mode.

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 content is front-loaded and sectioned clearly, which helps scanning, but the definition is padded with boilerplate headers and mild redundancy (the numeric-input requirement appears in two places). The RETURNS section earns its space only because no output schema exists.

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 two-parameter calculator with no output schema, the definition covers everything an agent needs: formula, bounds behavior, error semantics, sibling routing, and a full return-value breakdown including example display strings. Nothing material is left to inference.

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 units, defaults, and min/max bounds for both parameters. The description restates parameter names and units and ties them to the formula, but adds no syntax or interpretation detail beyond the schema, so 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 names the specific resource (Mean Arterial Pressure) and the exact computation (MAP = DBP + 1/3 × (SBP − DBP)), and it enumerates the concrete outputs (map_value, pulse_pressure, perfusion_status, cardiac_cycle_split). It also distinguishes itself from nearby siblings by naming omni_universal_query as the generic alternative.

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 and WHEN NOT TO USE blocks are present, including the exclusion of qualitative reasoning and non-numeric inputs. Alternatives are named with the condition that selects them: omni_batch_calculate for chained jobs and omni_describe_solver for schema inspection.

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