Water and steam saturation properties from the IAPWS-IF97 Region 4 equation. Give either temperature_c to get saturation pressure, or pressure_bara to get saturation temperature. Powered by multicalci.com.
| Name | Required | Description | Default |
|---|---|---|---|
| pressure_bara | No | Saturation pressure, bar absolute (0.0061 to 220.64) | |
| temperature_c | No | Saturation temperature, degC (0.01 to 373.946) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It implies a read-only calculation by stating it derives properties from an equation, and it mentions the external service 'Powered by multicalci.com.' However, it does not explicitly state that it is non-destructive, requires no special permissions, or describe error/edge-case behavior. The simple nature of a property calculator partly excuses this, but more transparency would be beneficial.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences front-load the purpose, then explain input modes. Every sentence earns its place with no filler. The 'Powered by' note is brief and adds relevant context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (2 parameters, no output schema, no nested objects). The description fully explains what the tool does, the exact inputs and their ranges, and the expected outputs (saturation pressure or temperature). It even names the governing equation. No significant information is missing for an engineer to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema covers 100% of parameter descriptions, giving ranges for pressure and temperature. The description adds crucial semantics by stating the parameters are mutually exclusive alternatives and what each returns (saturation pressure vs temperature). This goes beyond the schema's factual range information, clarifying intended usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool calculates water and steam saturation properties via the IAPWS-IF97 Region 4 equation, and explains the two modes: input temperature for pressure or input pressure for temperature. This specific verb+resource+scope distinguishes it from all sibling tools, which are for other engineering calculations like valve sizing or pressure drop.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit usage instructions are provided: 'Give either temperature_c to get saturation pressure, or pressure_bara to get saturation temperature.' This clarifies when to use the tool and how to invoke it. No explicit exclusions or alternative tool names are mentioned, but the sibling context makes the fit obvious.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct engineering calculation: valve sizing for gas vs liquid, compressibility, NPSH, orifice flow, pipe friction, pump power, steam saturation, and tank volume. There is no functional overlap that would confuse an agent.
All tool names use lowercase snake_case and clearly indicate the calculation subject, but there is slight inconsistency in ordering (e.g., control_valve_size_gas vs gas_z_factor_pr) and inclusion of standards/suffixes (pr, iso5167, if97). The pattern is still predictable and readable.
With 9 tools, the server is well-scoped for a specialized engineering calculation toolkit. Each tool serves a distinct purpose without redundancy, and the count is comfortably within the ideal 3-15 range.
The toolset covers core fluid handling and thermodynamic calculations (valve sizing, pipe flow, pump selection, steam properties, tank geometry). Minor gaps exist, such as heat exchanger calculations or relief valve sizing, but the provided set covers common process engineering needs without major dead ends.