Skip to main content
Glama
gchen19

AnkusDrive

by gchen19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Fluid Props

fluid_props
Read-only

Get thermophysical properties of a fluid (density, viscosity, cp, conductivity, Prandtl) at temperature and pressure for CFD/convection. Uses CoolProp, with constant fallback for air/water if absent.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
T_KYes
P_PaNo
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false, but the description adds rich behavioral detail: the CoolProp equation-of-state source, clean degradation to constant-fallback values for air/water, and a structured error tuple for unsupported fluids. This goes well beyond what annotations convey, so the agent knows exactly how the tool behaves in different environments.

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?

The description is information-dense and front-loaded with the core purpose, but it is relatively long. Almost every sentence earns its place, including the fallback behavior and return payload, though the parenthetical '(issue #100)' is incidental and adds little for an agent selecting the tool.

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 compensates by enumerating the return fields with units, explaining the fallback fidelity, and identifying the source citation. For a read-only property lookup with three parameters, this is complete enough for an agent to call it correctly and interpret results confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, so the description must carry the meaning of the parameters. It does: 'name' is explained with fluid examples, 'T_K' is specified as absolute temperature in K, and 'P_Pa' is given as pressure in Pa with a default of 1 atm. This fully compensates for the bare 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 opens with a specific verb and resource: 'Thermophysical properties of a fluid at (T, P) from CoolProp's equation of state.' It names the core inputs, example fluids, and the full return tuple, making the tool's function unmistakable. It also distinguishes its role by noting it is the 'DEFAULT fluid-property source behind the convection/CFD screens.'

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

Usage Guidelines5/5

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

The description explicitly states when this tool is used ('DEFAULT fluid-property source behind the convection/CFD screens') and when its results should not take precedence ('explicit caller props still override'). It also describes the fallback behavior when CoolProp is absent, giving an agent clear expectations about when the tool still returns useful values versus an error.

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