Skip to main content
Glama

NS Pros MCP Gateway

nist-fluid-properties__nist_fluid_list

List the ~76 fluids NIST's Chemistry WebBook carries full thermophysical property surfaces for (water, nitrogen, oxygen, argon, CO2, light hydrocarbons, refrigerants R11-RC318, and a few industrial gases). Optionally filter by a substring of the name or refrigerant code.

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": {
      "query": "R1"
    },
    "name": "nist-fluid-properties__nist_fluid_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional substring filter, e.g. "R1" or "propane". Omit to list all fluids.

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 must carry the behavior, and for a pure enumeration tool the implied read-only nature is clear from 'List'. It adds useful context the schema lacks: the data source (NIST Chemistry WebBook), the count (~76), and that matching applies to refrigerant codes as well as names. It does not address case sensitivity or what the list entries look like, which is the remaining gap.

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, front-loaded with the count and the scope, then the filtering rule. Every clause contributes: the parenthetical enumeration justifies why an agent should trust this list as authoritative coverage rather than guessing names.

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 single-optional-parameter list tool this is nearly complete: scope, source, filtering, and default behavior are all present. The one omission is the return shape, since no output schema exists and the description never says whether entries are bare names, name/code pairs, or objects.

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%, and the schema already documents the query parameter, its optionality, and the omit-to-list-all behavior. The description's 'substring of the name or refrigerant code' adds only marginal meaning beyond the schema's own examples ('R1', 'propane'), so the schema is doing the heavy lifting here.

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 (list) plus resource (fluids with full thermophysical property surfaces) and quantifies scope (~76 fluids) with concrete families enumerated. That enumeration, especially 'refrigerants R11-RC318', makes it plainly distinct from the sibling nist_fluid_properties and nist_fluid_saturation, which consume these names rather than enumerate them.

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?

The optional-filter framing makes the discovery use case evident: call with no query to enumerate everything, or pass a substring to narrow. It stops short of explicitly telling the agent to call this first to resolve a valid fluid identifier before invoking nist_fluid_properties, and names no exclusion conditions.

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.