subsea-flow-calculator

hydrate_equilibrium_approx

Estimates natural gas hydrate dissociation temperature using Towler-Mokhatab model to assess deepwater subcooling risk and determine thermal insulation needs.

Instructions

Estimates the natural gas hydrate formation equilibrium dissociation temperature (°C and °F) using the Towler-Mokhatab empirical model, calculating deepwater subcooling risk and thermal insulation requirements.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operating_pressure_bar": "<operating_pressure_bar>"
    },
    "name": "hydrate_equilibrium_approx"
  }
}

Input Schema

Name	Required	Description
`gas_specific_gravity`	No	Gas specific gravity relative to air (0.55 to 0.75 for sweet gas). Default: 0.65.
`seabed_temperature_c`	No	Seabed ambient temperature in degrees Celsius. Default: 4.0°C (standard deepwater abyss).
`operating_pressure_bar`	Yes	Operating or shut-in system pressure in absolute bar (20 to 250 bar).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 7, 2026

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden; it does disclose that results come from the Towler-Mokhatab empirical model, which usefully signals accuracy limits and applicability. However, it says nothing about output format beyond units, assumptions, or validity range, which matters for an empirical correlation.

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?

A single front-loaded sentence with no filler. The one weakness is that it packs two distinct claims (equilibrium temperature and subcooling/insulation analysis) into one clause, diluting the focus.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 naming the returned quantity and both units (°C and °F), and it sets the domain context. Minor gaps remain around the exact scope of the subcooling/insulation outputs, but nothing essential for invoking the tool is missing.

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%, with units, defaults, and valid ranges documented for all three parameters, so the schema does the heavy lifting. The description adds no parameter-level detail beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Estimates the natural gas hydrate formation equilibrium dissociation temperature') and names the empirical model used, which clearly separates it from siblings like meg_inhibitor_dosage and hydrostatic_pressure. The trailing clause about 'calculating deepwater subcooling risk and thermal insulation requirements' slightly muddies the scope, implying additional derived outputs that may or may not be returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The deepwater/subcooling framing implies the operating context in which this tool applies, but it never states when to use it versus alternatives or any prerequisites. No exclusions or sibling comparisons are given, so usage must be inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server