Skip to main content
Glama

Steady conduction through a wall

bpj_eng_plane_wall_loss
Read-onlyIdempotent

Estimate one-dimensional steady heat flow through a homogeneous plane layer.

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": {
      "k": "<k>",
      "thickness": "<thickness>",
      "area": "<area>",
      "delta": "<delta>"
    },
    "name": "bpj_eng_plane_wall_loss"
  }
}

Input Schema

NameRequiredDescriptionDefault
kYes
areaYes
deltaYes
thicknessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds the modelling assumptions (one-dimensional, steady, homogeneous), but it does not state the output quantity or units, sign convention for delta, or behavior at delta=0. That is meaningful context but incomplete for a calculation tool.

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 12-word sentence with no filler and the key physical scope front-loaded. It is efficiently structured, though the terseness contributes to gaps elsewhere rather than being a flaw in conciseness.

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

Completeness2/5

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

This is a simple 4-parameter calculation with no output schema, so the description should ideally state the returned quantity/units and key assumptions. It gives the model assumptions but omits return semantics and parameter roles, leaving the definition under-specified relative to its complexity.

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%; the schema titles supply parameter names and units but no explanatory descriptions. The description does not explain k, thickness, area, or delta, nor how they combine. It adds almost no meaning beyond the parameter titles.

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?

The description states a specific verb ('Estimate') and physical resource ('heat flow through a homogeneous plane layer') and narrows to one-dimensional steady conduction, which distinguishes it from transient or convective siblings. It does not name a sibling alternative or mention the Fourier-law formula, but the scope is clear.

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 explicit when-to-use guidance, prerequisites, or exclusions are given. The physics wording implies the domain, but there is no statement about when to choose this over convective transfer or heat-exchanger LMTD, and no note that transient or multilayer cases are out of scope.

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.