Skip to main content
Glama

Heat exchanger log mean difference

bpj_eng_heat_exchanger_lmtd
Read-onlyIdempotent

Find log mean temperature difference from two positive terminal differences in a heat exchanger.

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": {
      "endA": "<endA>",
      "endB": "<endB>"
    },
    "name": "bpj_eng_heat_exchanger_lmtd"
  }
}

Input Schema

NameRequiredDescriptionDefault
endAYes
endBYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, idempotent calculation, so the description need not repeat that. It adds the useful domain constraint that the terminal differences must be positive, but it omits behavioral details such as what happens when the two terminal differences are equal, where the LMTD formula is singular.

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?

The definition is a single front-loaded sentence with no filler. Every phrase contributes to identifying the calculation, its domain, and its inputs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter calculation, the core purpose is clear, but there is no output schema, so the description should ideally state the return value and units. It also omits the important equal-terminal-difference edge case that affects how the LMTD is computed.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for parameter meaning. It says there are two positive terminal differences, but the schema titles already identify them as terminal differences in K and enforce positivity via the minimum, so the description adds little beyond the schema. It also does not explicitly map endA and endB to the first and second terminal differences or clarify the formula.

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 states a specific verb, 'Find', and a specific resource, 'log mean temperature difference', plus the domain 'heat exchanger' and the two input quantities. It clearly distinguishes this calculation from the nearby heat-transfer siblings such as sensible heat, latent heat, and convective transfer.

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

Usage Guidelines2/5

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

The heat-exchanger context implies where the calculation applies, but there is no explicit guidance on when to use this tool versus alternatives or on prerequisites. No exclusions, edge cases, or sibling comparisons are given.

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.