Skip to main content
Glama

NS Pros MCP Gateway

nist-fluid-properties__nist_fluid_properties

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.

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,
      "temperature": 25,
      "pressure_unit": "atm",
      "temperature_unit": "C"
    },
    "name": "nist-fluid-properties__nist_fluid_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
fluidYesFluid name, formula or refrigerant code, e.g. "water", "CO2", "R134a", "nitrogen".
pressureYesPressure at which to evaluate properties.
temperatureYesTemperature at which to evaluate properties.
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.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden and does well: it discloses the return content, guarantees 'Every value carries its unit,' and reports phase (liquid/vapor/supercritical). It omits error behavior outside the fluid's valid range, numeric precision/reference state, and result structure, which is meaningful for a lookup tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: a front-loaded output-and-input specification followed by a short prerequisite. The long property list is dense but earns its place because it defines the tool's full return surface, and there is no filler or repetition of the schema.

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 five parameters, no annotations, and no output schema, the description covers what is returned, unit guarantees, and fluid breadth, which is enough to call it correctly. The remaining gap is failure and range behavior when the requested temperature/pressure falls outside a fluid's valid region, which an agent would need to interpret errors.

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%, with per-parameter descriptions and enums for both unit fields, so the schema already does the heavy lifting and baseline 3 applies. The description adds only marginal semantics beyond that, notably the breadth of accepted fluid identifiers ('water, nitrogen, oxygen, argon, CO2, hydrocarbons, refrigerants') and the unit defaults already stated in the schema.

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 exact verb-level outcome ('Density, specific volume, internal energy, enthalpy, entropy, Cv, Cp, speed of sound, Joule-Thomson coefficient, viscosity, thermal conductivity and phase') and the input domain (~76 NIST reference fluids at a given temperature and pressure). The 'at a given temperature and pressure' phrasing implicitly separates it from the saturation sibling, which is a T- or P-only lookup.

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 routing rule: 'Call nist_fluid_list first if unsure a fluid is covered,' including example fluid names to help matching. It stops short of stating when to prefer nist_fluid_saturation (e.g. at saturation conditions) or what to do for out-of-range states, so the guidance is clear but not exhaustive.

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.