Skip to main content
Glama

Phase-change heat

bpj_eng_latent_heat
Read-onlyIdempotent

Calculate the energy absorbed or released during a phase change at constant temperature.

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": {
      "mass": "<mass>",
      "latent": "<latent>"
    },
    "name": "bpj_eng_latent_heat"
  }
}

Input Schema

NameRequiredDescriptionDefault
massYes
latentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description confirms this is a pure computation but does not state the underlying relation (energy = mass x latent heat), whether the product is in kJ or J, or how sign conventions indicate absorption vs release. Some value added, but modest.

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?

A single well-formed sentence with the key constraint ('constant temperature') front-loaded and no redundant wording. It is arguably under-loaded rather than over-long: one more clause on output units or the formula would cost nothing.

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 two-parameter pure calculator with full annotation coverage, the description conveys the purpose adequately. However, the missing output unit and sign convention leave a real gap for an agent that must report or chain the result, and no output schema exists to fill it.

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% and the description never mentions 'mass' or 'latent' at all. The schema's own titles carry the units (kg, kJ/kg), which saves it from a 1, but the description contributes no meaning about how the two inputs interact or what units the result uses.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb-and-resource pair: calculating energy absorbed or released in a phase change, qualified 'at constant temperature'. That qualification implicitly separates it from the sensible-heat sibling, which involves temperature change, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

The phrase 'during a phase change at constant temperature' implies the applicable condition (melting/boiling/vaporizing rather than heating a single phase), so usage is inferable. There is no explicit when-to-use or when-not-to-use statement and no pointer to bpj_eng_sensible_heat for the temperature-change case.

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.