Skip to main content
Glama

Sensible heat requirement

bpj_eng_sensible_heat
Read-onlyIdempotent

Find ideal sensible heat from mass, specific heat, and temperature difference at constant phase.

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>",
      "cp": "<cp>",
      "delta": "<delta>"
    },
    "name": "bpj_eng_sensible_heat"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpYes
massYes
deltaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds the 'ideal' and 'constant phase' assumptions, which are useful, but does not explain output units, sign convention, or limits.

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?

One front-loaded sentence with no redundant wording. It is tight and appropriately sized for a simple three-parameter calculation.

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 simple, side-effect-free engineering calculation with complete annotations and no output schema, the definition covers the inputs and core assumption. It could state the output unit or explicit formula, but little essential information is missing.

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 description coverage is 0%, so the description must carry parameter meaning. It names all three inputs and maps them to the sensible-heat relationship, adding some meaning beyond the schema titles, but it does not specify the formula, sign convention, or that delta may be zero.

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 ('Find') and the computed quantity ('ideal sensible heat'), plus the three required inputs. 'At constant phase' implicitly distinguishes it from latent heat, but no sibling tool is named.

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?

Does not explicitly say when to use this versus bpj_eng_latent_heat or other thermal tools, and gives no exclusions. 'At constant phase' implies the no-phase-change case, so guidance is present but only implied.

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.