Skip to main content
Glama

NTC beta temperature

bpj_bench_thermistor_beta
Read-onlyIdempotent

Estimate NTC temperature using the single-beta model with a known resistance at a reference 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": {
      "resistance": "<resistance>",
      "referenceR": "<referenceR>",
      "referenceT": "<referenceT>",
      "beta": "<beta>"
    },
    "name": "bpj_bench_thermistor_beta"
  }
}

Input Schema

NameRequiredDescriptionDefault
betaYes
referenceRYes
referenceTYes
resistanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so no credit there. Beyond that the description only hints that results are an 'estimate' from a simplified model; it never states output units, the assumed beta-model accuracy range, or that validity degrades far from the reference temperature.

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?

One sentence, front-loaded with the verb and model, with no filler. It is efficient but so terse that it leaves the ambiguous resistance roles unexplained.

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?

Four required numeric parameters, zero schema descriptions, and no output schema — the description must carry all the meaning and does not. Missing output units (C vs K), the direction of the equation, and the interpretation of the two resistance fields leave real gaps for an agent to guess at.

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 coverage is 0% — only bare titles like 'Beta (K)' and 'Reference temperature (C)' exist. The description mentions a 'known resistance at a reference temperature' but does not disambiguate which of 'resistance' vs 'referenceR' is the measured value versus the calibration point, nor explain how referenceT anchors the conversion.

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?

Names a specific verb ('Estimate'), resource ('NTC temperature'), and method ('single-beta model'), which is enough to distinguish it from generic temperature/unit siblings like bpj_units_temperature or bpj_eng_mix_temperature. It stops short of explicitly contrasting with any sibling, keeping it below a 5.

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?

There is no when-to-use statement, no mention of prerequisites (e.g., that beta must be a datasheet value, or when the single-beta model is preferred over a Steinhart-Hart fit), and no alternative tool named. The purpose implies a context, but no guidance is actually 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.