Skip to main content
Glama

Fluid Props

fluid_props
Read-only

Returns density, viscosity, specific heat, thermal conductivity, and Prandtl number for a named fluid at a given temperature and pressure via CoolProp, with air/water fallback constants.

Instructions

Thermophysical properties of a fluid at (T, P) from CoolProp's equation of state (issue #100). name is a fluid (e.g. 'water', 'air', 'R134a', 'CO2', 'nitrogen'), T_K absolute temperature [K], P_Pa pressure [Pa, default 1 atm). Returns {ok, density [kg/m³], viscosity [Pa·s], cp [J/kg·K], conductivity [W/m·K], prandtl, kinematic_viscosity [m²/s], fidelity, valid_range_ok, source, warnings, coolprop_available}. This is the DEFAULT fluid-property source behind the convection/CFD screens; explicit caller props still override. Degrades cleanly when the (opt-in) CoolProp extra is absent: air/water return ≈20 °C constants (fidelity='constant_fallback'); other fluids return {ok:false, reason, install}. CoolProp (BSD-3) is cited as the source.

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": {
      "name": "<name>",
      "T_K": "<T_K>"
    },
    "name": "fluid_props"
  }
}

Input Schema

NameRequiredDescriptionDefault
T_KYes
P_PaNo
nameYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the constant_fallback degradation path for air/water without the CoolProp extra, the {ok:false, reason, install} failure shape for other fluids, and the fidelity/valid_range_ok/warnings fields. That is exactly the behavioral context an agent needs before trusting a returned viscosity or cp.

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?

Front-loaded with the one-line purpose, then parameters, then return shape, then fallback behavior. It is dense but slightly overstuffed — the '(issue #100)' and 'CoolProp (BSD-3) is cited as the source' fragments do not help an agent call it correctly.

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?

With no output schema, the description supplies the full return-key list, and it covers the fallback semantics, fidelity flag, and override precedence. An agent can call this correctly and interpret every result without further documentation.

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 only 25% (only `workspace` is documented), so the description must carry the load, and it does: it enumerates valid fluid names (water, air, R134a, CO2, nitrogen), gives T_K in kelvin and P_Pa in pascals with a 1 atm default. It omits any mention of `workspace` and of valid T/P ranges, keeping it off a 5.

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?

States a specific verb+resource: thermophysical properties of a fluid at (T,P) via CoolProp's equation of state. Clearly distinct from siblings like material_get, h_estimate, or cfd_pipe_flow, which do not return CoolProp state properties.

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?

Explicitly frames itself as the DEFAULT fluid-property source behind the convection/CFD screens and notes that explicit caller props still override, which tells the agent when this is the right choice. It never names a concrete alternative sibling (e.g. material_get) or states when not to use it, so it stops short of a 5.

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