Skip to main content
Glama

Two-point sensor calibration

bpj_bench_sensor_linear_scale
Read-onlyIdempotent

Calibrate a linear sensor with two raw/reference pairs and transform a third raw reading.

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": {
      "rawA": "<rawA>",
      "refA": "<refA>",
      "rawB": "<rawB>",
      "refB": "<refB>",
      "reading": "<reading>"
    },
    "name": "bpj_bench_sensor_linear_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawAYes
rawBYes
refAYes
refBYes
readingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish that this is read-only, idempotent, non-destructive, and closed-world. The description adds that it performs a two-point linear calibration and transforms a third reading, but it does not disclose the transformation formula, extrapolation behavior, handling of identical raw points, or return format.

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?

The description is a single front-loaded sentence with no filler. It states the operation and the inputs efficiently.

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 five-parameter calibration calculator with no output schema, the description conveys the core input requirements but omits important context: the linear transformation method, behavior when the two raw points are equal, and what exactly is returned. It is minimally adequate but leaves meaningful gaps.

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 partially compensates by identifying two raw/reference pairs and a third raw reading, which maps onto the five fields, but it does not explain the raw-versus-reference distinction, the role of each pair, or constraints such as rawA differing from rawB.

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 gives a specific verb ('Calibrate') and resource ('a linear sensor'), and it clarifies that the operation consumes two raw/reference calibration pairs plus a third raw reading. It does not explicitly contrast itself with sibling tools, but the purpose is unambiguous.

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?

Usage is implied by the required input pattern: use this when you have two raw/reference calibration pairs and one new raw reading to transform. There is no explicit when-not guidance, no mention of alternatives, and no prerequisite such as requiring the two raw points to be distinct.

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.