Skip to main content
Glama

NS Pros MCP Gateway

nist-fluid-properties__nist_fluid_saturation

Liquid/vapor saturation (phase-boundary) properties for one of NIST's ~76 reference fluidsgive EITHER a saturation temperature (returns the matching saturation pressure, e.g. boiling point at 1 atm) OR a saturation pressure (returns the matching saturation temperature), plus density, enthalpy, entropy, viscosity, thermal conductivity and surface tension on both the liquid and vapor side of the boundary. Do not pass both temperature and pressure.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fluid": "water",
      "pressure": 1,
      "pressure_unit": "atm"
    },
    "name": "nist-fluid-properties__nist_fluid_saturation"
  }
}

Input Schema

NameRequiredDescriptionDefault
fluidYesFluid name, formula or refrigerant code, e.g. "water", "propane", "R134a".
pressureNoSaturation pressure to evaluate. Omit if passing `temperature` instead.
temperatureNoSaturation temperature to evaluate. Omit if passing `pressure` instead.
pressure_unitNoUnit of `pressure`. Default "atm".
temperature_unitNoUnit of `temperature`. Default "C".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden, and it does disclose the exchange relationship (T yields P and vice versa) plus the full payload across both liquid and vapor sides. It omits practical traits such as valid saturation ranges, behavior for fluids lacking surface tension, and error handling when a fluid name is unrecognized.

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?

Purpose and the either/or rule are front-loaded, and the trailing 'Do not pass both' sentence is a useful guardrail. The single long sentence with an enumerated payload is dense but each element is informative; there is a minor typo ('fluidsgive') and no wasted framing.

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?

For a 5-parameter tool with no annotations and no output schema, the description covers the essentials: what comes back on both phases and the mutual exclusivity constraint. Remaining gaps — saturation-range validity, surface-tension availability, and how to resolve fluid identifiers — are real but secondary given the rich schema descriptions.

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 coverage is 100%, so a baseline of 3 applies, but the description earns an extra point by explaining the semantic coupling of the temperature and pressure parameters (each determines the other) and illustrating it with a physical example rather than repeating the schema text.

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 states a precise verb+resource: it returns liquid/vapor phase-boundary (saturation) properties for one of ~76 NIST reference fluids, and enumerates the returned quantities. The phrase 'saturation (phase-boundary)' cleanly separates it from single-state property lookups such as nist_fluid_properties without needing to name a sibling.

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

Usage Guidelines4/5

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

It gives a concrete usage rule — supply EITHER temperature OR pressure, never both — and grounds it with a worked case ('boiling point at 1 atm'). It stops short of routing to alternatives (e.g., nist_fluid_list for resolving fluid names, or the single-phase property tool), so it is clear but not fully discriminating.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.