Skip to main content
Glama

Surface convection heat transfer

bpj_eng_convective_transfer
Read-onlyIdempotent

Estimate convective heat transfer for a specified film coefficient, area, and temperature difference.

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": {
      "coefficient": "<coefficient>",
      "area": "<area>",
      "delta": "<delta>"
    },
    "name": "bpj_eng_convective_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYes
deltaYes
coefficientYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds nothing beyond that: it does not state the underlying relation (Q = h·A·ΔT), what unit the returned value is in, or whether 'Estimate' implies approximation. For a pure calculator a little formula-level disclosure would have been cheap and useful.

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 front-loaded sentence with no filler or repetition. It is efficient, though the terse one-liner format leaves no room for the usage or output context that would have helped.

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 three-parameter deterministic calculator with no output schema, the definition covers what the tool consumes but not what it produces (result quantity and units) nor any edge-case note such as delta=0 yielding zero transfer. Minimal but not clearly wrong for the complexity involved.

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%, but the properties carry titles with units (m2, K, W/m2 K). The description names all three parameters in physical terms, compensating for the coverage gap at minimum level, yet adds no semantics beyond the titles — e.g. it never says whether a positive or negative delta is expected or how the inputs combine.

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+resource: 'Estimate convective heat transfer', with the three governing inputs named. It is distinguishable from siblings such as bpj_eng_plane_wall_loss (conduction) or bpj_eng_latent_heat by the word 'convective' and the film-coefficient input, though it never explicitly contrasts itself with them.

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?

No when-to-use or when-not-to-use guidance, no prerequisites, and no pointer to alternative heat-transfer tools. The only hint is the phrase 'for a specified film coefficient, area, and temperature difference', which describes inputs rather than selecting 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.