"Oxygen" matching MCP tools:

• plan_blendA

  Dive KitA

  Returns a partial-pressure blending plan from what a cylinder holds to a target mix and pressure: bleed, helium, oxygen and top-up steps with the gauge pressure to stop at, the mix after each step, the cooling step, the mix achieved, the gas drawn from each bank and alternative plans. Use this when a diver or blender asks how to fill nitrox or trimix ("fill my twin 12s to 21/35 from 60 bar of 18/45") or whether their banks can reach a mix. Not for a fill already done (mix_result), continuous-flow blending (blend_continuous) or decanting (decant). current is the cylinder as analysed now: oxygen_pct, helium_pct, pressure, and preset or cylinder_size as in plan_dive (default AL80 size). target: oxygen_pct, helium_pct, pressure. banks default to unlimited air, oxygen and helium; a finite bank needs pressure and cylinder_size together. A target the banks cannot reach returns feasible false with the reason and the partial plan, not an error. To verify, send mix_result_current and mix_result_additions to mix_result; then gas_specs, and plan_dive with the analysed mix. Oxygen above 40% needs oxygen-clean equipment and blender training. No engine call. Example: {"current":{"oxygen_pct":21,"pressure":50,"preset":"twin_12l"},"target":{"oxygen_pct":21,"helium_pct":35,"pressure":220}}

  ConnectorNo auth

• blendA

  In Da MixA

  Use whenever the user asks how to blend, mix, fill or prepare a breathing gas, even if they don't mention In Da Mix. Step-by-step fill plan for blending nitrox, trimix, heliair or heliox into a scuba tank, from what is in it now to the mix and pressure wanted: how much helium and oxygen to add, the order, cooling waits, the O2 test, the air top-up, and booster bars. Partial pressure or continuous, with the app's calculation methods. Use for "how do I blend 18/45 to 220 bar", "how much O2 do I add for EAN32", "fill from the gas left in the tank", "kako napraviti trimix 12/65", "koliko helija trebam za 200 bara", "napravi plan punjenja boce". Needs the target mix and pressure, and what is in the tank now: if the start is unknown, ask; never assume an empty tank. The method, temperature and banks come from the settings. Answer: the start gas, the target, the additions in order with their pressures, the resulting mix, and the key filling and analysis precautions. Then ask whether to calculate the gas this fill takes from the source banks (gas_usage).

  ConnectorNo auth

• read_share_linkA

  Dive KitA

  Decodes a Dive Kit share link (https://divekit.app/share/deco-plan/...) into the plan_dive input it carries: profile, gases, CCR rig, settings, custom contingencies, modifiers and repetitive tissue state, in the requested units. Use this when a diver pastes a Dive Kit link and wants the plan recomputed or changed. Not for links from other apps, and not a schedule: it returns inputs. Results baked into the link are ignored; plan_dive recomputes them. Links do not carry behavior.stay_on_loop or the loop oxygen-break toggle, so those return as defaults and the result says so.

  ConnectorNo auth

• mix_resultA

  Dive KitA

  Returns the mix and pressure a cylinder ends with after gases are added in order: each addition's pressure and mix before and after, the cooling step, and the final O₂ %, He % and pressure. Use this when a diver or blender asks what a fill produced ("50 bar of air, 40 bar of oxygen, then air to 200"), or to check a plan_blend plan: send its mix_result_current as current and its mix_result_additions as additions. Not for planning toward a target (plan_blend) or joining two cylinders with a whip (decant). Pressures are gauge (bar or psi, per units); mixes are O₂ % and He %. environment sets altitude and the ambient and fill temperatures (defaults sea level, 20 °C, fill equal to ambient); a hot fill settles lower. Real-gas mixing. Analyse the cylinder once it has cooled: the analysed mix, not this one, goes into plan_dive. No engine call. Example: {"current":{"oxygen_pct":21,"pressure":50},"additions":[{"oxygen_pct":100,"pressure_added":35},{"oxygen_pct":21,"pressure_added":115}]}

  ConnectorNo auth

• get_trainingA

  NolioA

  Read one completed workout or race in full: duration, distance, load, heart rate, power, the athlete's debrief, and on request its laps and its sensor curves. `id`: the trn_… (workout) or cmp_… (race) handle of a row returned by get_calendar(mode='real'). `athlete`: the managed athlete's usr_… handle when the workout is not yours. `laps`: add every lap, the ones recorded by the device first, then the ones drawn in Nolio, each with its `stats` as {value, unit}. When the connector's terms withhold them, only the laps drawn in Nolio come, with null `stats`, and `laps_restriction` says why. `streams`: the sensor curves to add, among heartrate, watts, cadence, torque, pace (a speed in m/s), altitude, distance, or the key of another curve of the file. `time` (seconds from the start) always comes with them, `units` gives each curve's unit. Ask only for the curves the question needs; a file-less workout returns `available: false`. Each curve is sampled evenly to `max_points` (default 600), `every_nth_sample` says the step; `max_points` can go higher, within 6000 points across the curves requested (`time` aside). `from_index` / `to_index` keep one window of samples, both included: a lap's `start_index` and `end_index` give exactly that lap. The response then carries `from_index`: point i of a curve is sample from_index + i * every_nth_sample. Files often hold more curves than these seven: ground contact time, vertical oscillation and ratio, stride length, running form power and leg stiffness, breathing rate, muscle oxygen (SmO2, THb), core and skin temperature, glucose, pedal smoothness and torque effectiveness, gears, stroke rate. Their keys vary by device: whenever you request a curve, `other_streams` lists the ones this file holds (key, name, unit); request them by key. A requested curve the file does not hold comes back in `unknown_streams`.

  ConnectorOAuth

• noaa_marine_get_ocean_observationsA

  noaa-marine-mcp-serverA

  Live sub-surface oceanographic observations from an NDBC station's water-quality sensors: at each reported depth, water temperature, conductivity, salinity, dissolved oxygen as both saturation percent and concentration in ppm, chlorophyll, turbidity, pH, and redox potential. This is the water-column counterpart to noaa_marine_get_conditions, which returns surface meteorological and wave data — use this tool for what the water is doing below the surface, that one for weather and sea state at the buoy. It returns the most recent observation as one reading per reported depth, and most stations report a single depth while some report several at the same time; sensor coverage is sparse, most stations populating only water temperature and salinity, and any value the station did not report comes back null rather than a fabricated zero, as do latitude and longitude for a station absent from the NDBC active-stations list. Sub-surface sensors are on only a subset of NDBC stations, so find one with noaa_marine_find_stations using source="ndbc" and types=["water_quality"], which filters on NDBC's own water-quality catalog flag — the flag and actual .ocean availability drift, so this tool reads any station that serves the file and returns observations_not_found for one that does not.

  ConnectorNo auth

• what_ifA

  In Da MixA

  What mix you get when you add given pressures of oxygen, helium and/or air to what is in the tank (the app's What If): the pressure after each addition, the resulting mix, its MOD, EAD, END and gas density. Use for "what if" additions: "I have 50 bar of air, what do I get if I add 30 bar of O2 and top up with 120 bar of air", "what if I add 40 bar of helium", "što dobijem ako dodam 30 bara kisika", "dodam 40 bara helija, što dobijem". what_if: given additions -> the resulting mix; blend: a target mix -> how to make it. Pass only the additions and the tank's start the user gave. Answer: the start, the additions in order, the final pressure, the resulting O2 and He, and its MOD by the settings. Then ask whether to check its complete MOD or to adjust the additions for a target mix (blend).

  ConnectorNo auth

• get_fishingA

  Crosby, TX WeatherA

  Live water conditions for the waters people fish near Crosby, TX — Lake Houston, the San Jacinto River forks, the Trinity River, and nearby bayous — from USGS real-time monitoring. Full stations report temperature, dissolved oxygen, pH, and turbidity; some fished bayous report water level only. A nearby-station reading, not the exact fishing spot, and conditions rather than a guaranteed bite.

  ConnectorNo auth

• current_conditionsA

  usgswaterA

  Latest instantaneous (real-time) readings for one or more USGS gauge sites. Returns the most recent value per site × parameter — e.g. current streamflow and gage height for a river. Common parameter codes: 00060 = discharge/streamflow (ft³/s), 00065 = gage height (ft), 00010 = water temperature (°C), 00045 = precipitation (in), 00095 = specific conductance, 00300 = dissolved oxygen, 63680 = turbidity. Keyless.

  ConnectorNo auth

• current_conditionsA

  Usgs WaterA

  Latest instantaneous (real-time) readings for one or more USGS gauge sites. Returns the most recent value per site × parameter — e.g. current streamflow and gage height for a river. Common parameter codes: 00060 = discharge/streamflow (ft³/s), 00065 = gage height (ft), 00010 = water temperature (°C), 00045 = precipitation (in), 00095 = specific conductance, 00300 = dissolved oxygen, 63680 = turbidity. Keyless.

  ConnectorNo auth

• best_mixA

  Dive KitA

  Use this when the diver asks what gas to breathe at a depth or which deco gases to carry: returns the richest bottom mix within a PPO₂ limit (default 1.4 bar) and an END limit (default 30 m, 98 ft), the nearest standard fill inside the same limits, and the standard deco gas ladder for that depth with switch depths. Not for checking one named gas (gas_specs) or planning the dive (plan_dive). The ladder is the common choice, not a prescription: none to 30 m, EANx50 to 45 m, EANx50 and oxygen to 60 m, and a travel gas deeper. A bottom mix under 18% O₂ needs descent_gas in plan_dive. No engine call. Example: {"depth":50}

  ConnectorNo auth

• lookup_referencesA

  Dive KitA

  Returns vetted references from Dive Kit's open references dataset, with links. Use this when a diver asks for a source. Call it before answering any question about deco theory, physiology, gas limits, blending practice, standards or training, so the answer names its source. Not for calculations. If nothing matches, the result lists where to search next; say that source is not Dive Kit-vetted. Each reference gives title, authors, year, type, publisher, link or DOI, access, and what it is authoritative for (gradient factors, oxygen toxicity, gas density, blending and oxygen cleaning, real gas, buoyancy, gas management, training). Not for cylinders (lookup_cylinders) or courses (lookup_certifications). topic narrows by subject and type by kind of source; the enums are in the input schema. query matches every word against the title, authors, publisher, notes and what the source is authoritative for. This is Dive Kit's own curated data (MIT licence, open.divekit.app), not a web search. No engine call. Example: {"topic":"gradient_factors"}

  ConnectorNo auth

• decantA

  In Da MixA

  Decanting one gas (oxygen, or helium) from source cylinders into a small cylinder without a compressor, as the app's Decant: a cascade, each cylinder equalised in turn (ideal gas). plan refills: one refill or a series (e.g. a CCR O2 cylinder from 75 to 150 bar after every dive): which cylinders each refill uses, the pressures after, how many refills the cylinders give, why it stops, and how many cylinders would be needed. plan diving_days: the app's diving-days planner (use per day, dives a day, Extra cylinders). For linked banks or a booster use fills_from_bank. Prefer it for CCR oxygen logistics. Use for "how many 3 L O2 cylinders do I need to refill my 2 L CCR cylinder after 10 dives", "how many CCR diving days do these O2 cylinders give", "koliko dana mogu roniti s ovim bocama kisika", "koliko puta mogu pretočiti kisik". Don't invent cylinders and don't change the user's gas use per dive or per day. Answer for refills: the number of complete refills, which cylinders each uses, the pressures after where useful, the cylinder that limits it, and why one more refill isn't possible. Answer for diving days: the days, dives a day, use per day, the pressures it keeps to, the cylinders used, and the Extra cylinders. Then ask whether to compare with an extra cylinder, another start pressure or another daily use.

  ConnectorNo auth

• medicare_dmepos_rateA

  Medicare PricingA

  What does Medicare pay for a piece of durable medical equipment, prosthetic, orthotic, or medical supply (DMEPOS)? Returns the fee-schedule amount for a HCPCS Level II code (E/K/L/A-codes — CPAP machines, wheelchairs, ostomy supplies, braces, oxygen equipment...) in a given US state, with SEPARATE rural and non-rural amounts, since Medicare pays DMEPOS by state rather than by the physician-fee-schedule locality. Answers "how much does Medicare pay for a CPAP machine (E0601)", "DMEPOS rate for a wheelchair in Texas", "what is the rural rate for this HCPCS code in Montana". Unlike medicare_physician_payment, this DOES include the HCPCS code description — DMEPOS uses HCPCS Level II, which CMS itself maintains and is not AMA copyright (CPT/HCPCS Level I is). States the fee-schedule YEAR and RELEASE (quarterly-ish: A=January, B=April, C=July, D=October) used on every response, and the modifier resolved (many DMEPOS codes price differently for rental "RR" vs. new purchase "NU" vs. used "UE" — pass one if you know it, otherwise the first modifier on file for the code is used and stated).

  ConnectorNo auth

• blend_continuousA

  Dive KitA

  Returns the settings for continuous-flow blending through a compressor intake: each feed gas's share of the intake flow, the analyzer readings to aim for after the first injection and at the end, and the pressure to bleed to first when the cylinder's gas is in the way. Use this when a blender fills with fixed air, oxygen and helium feeds (a nitrox stick or membrane) and asks what ratios or analyzer targets give a mix. Not for partial-pressure fills (plan_blend). current is the cylinder now, as in plan_blend; target: oxygen_pct, helium_pct, pressure. injection_order he_first (default) or o2_first picks which intermediate analyzer reading the text leads with; both come back. bleed_step rounds the bleed down to a gauge mark, default 5 bar (100 psi). An impossible mix returns feasible false with the reason. No engine call. Example: {"current":{"oxygen_pct":21,"pressure":0},"target":{"oxygen_pct":32,"pressure":200}}

  ConnectorNo auth

• top_upA

  In Da MixA

  Top a tank up with a ready-made supply gas (air, EAN32, a trimix premix…): the pressure added, the mix you end up with, its MOD, and the gas density at a depth. For a ready-made supply gas; to add pure oxygen or helium use what_if or blend. Use for "I have 50 bar of EAN32 left, what do I get if I top up with air to 200", "dopuni mi bocu s 50 bara EAN32 zrakom do 220 bara", "koji će biti konačni postotak kisika". Needs the start pressure and mix, the final pressure and the supply gas: ask if one is unknown, don't assume. Answer: the start, the gas added and the final pressure, the resulting mix, and its MOD by the settings. Then ask whether to check the mix for a planned depth (mod, with the complete MOD).

  ConnectorNo auth

• running_economyA

  ham.runA

  Compute oxygen cost of running (Cr in mL O₂·kg⁻¹·m⁻¹) given pace, gradient, surface, shoe type, and athlete characteristics. Returns full multiplicative breakdown. Source: ham.run running-economy module (Barnes & Kilding 2015 + Minetti 2002).

  ConnectorNo auth

• covair_verifyA

  CovaSyn Chemistry ToolsC

  Verify a structure against a measured IR spectrum: verdict, band recall, and what is left unexplained. Pass `path` whenever you have the spectrum file. The curve is baseline-corrected and normalised the way covair_auto_analyze does it, and the verdict then requires two things: that the structure's expected bands were found AND that the structure accounts for the absorption actually measured. With neither a `path` nor peaks there is nothing to verify against and the verdict is `no_evidence` -- not `inconsistent`, which would assert evidence against the structure where none was supplied. With peaks but no curve, `verdict_basis` reads `peak_recall_only` and the verdict cannot reach `consistent`. Do NOT read a verdict off `match_score`. It is the fraction of the CANDIDATE's own expected bands that were found, so the denominator belongs to the candidate and a structure predicting few bands scores high on any spectrum. Measured on a real aspirin spectrum: hexane, which contains no oxygen, scores 1.00 where aspirin scores 0.92, because all four of hexane's expected bands are C-H. Read `match_score` with `n_expected_bands` beside it; `band_recall_verdict` shows what recall alone would have concluded, and `verdict_note` says in words why the verdict differs. Two measured limits. This blocks the "explains almost nothing" class, not wrong structures in general -- nitrobenzene still reads `consistent` against an aspirin spectrum. And on featureless input the unexplained-absorption test collapses onto its chance level, so a broad candidate can pass on noise; check `claimed_axis_fraction` in that case.

  ConnectorAPI key

• nist_fluid_propertiesA

  Nist Fluid PropertiesA

  Density, specific volume, internal energy, enthalpy, entropy, Cv, Cp, speed of sound, Joule-Thomson coefficient, viscosity, thermal conductivity and phase (liquid/vapor/supercritical) for one of NIST's ~76 reference fluids (water, nitrogen, oxygen, argon, CO2, hydrocarbons, refrigerants...) at a given temperature and pressure. Every value carries its unit. Call nist_fluid_list first if unsure a fluid is covered.

  ConnectorNo auth

• get_spo2A

  Oura MCPA

  Get nightly blood-oxygen (SpO2) average and breathing disturbance index for a date. Useful for altitude effects, suspected sleep apnea, or illness tracking. Pass user's LOCAL date as strict YYYY-MM-DD.

  ConnectorOAuth

• fitbit_spo2A

  Fitbit MCP by usefulapiA

  Blood oxygen saturation (SpO2) summary for a date or range. Fitbit REST: GET /1/user/-/spo2/date/{date}[/{endDate}].json.

  ConnectorNo auth