Skip to main content
Glama

Indoor dew point estimate

bpj_eng_air_dew_point
Read-onlyIdempotent

Estimate dew point over liquid water using the Magnus approximation for common indoor conditions.

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": {
      "airC": "<airC>",
      "rh": "<rh>"
    },
    "name": "bpj_eng_air_dew_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
rhYes
airCYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful method context ('Magnus approximation', 'over liquid water' rather than over ice) that is not in the structured fields, but it omits accuracy limits, behavior at the range edges, and what the returned value looks like.

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 wasted wording, naming the method and validity domain immediately. It is efficient, though it errs slightly toward under-specification for a tool with two undocumented parameters.

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?

With no output schema, the description should indicate the returned quantity and units (dew point in degrees C), which it never does. For a simple two-parameter calculator this is a notable but not fatal omission; the method and domain are otherwise adequately covered.

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%, so the description is expected to compensate, and it does not: neither 'airC' nor 'rh' is mentioned, and their units and required status are conveyed only by the schema titles. The one useful scoping hint ('common indoor conditions') is vague rather than a concrete constraint on the two inputs.

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 and resource ('Estimate dew point') plus the method and regime ('Magnus approximation', 'over liquid water'), which lets an agent distinguish this from the other bpj_eng_* calculators at a glance. It does not name a specific sibling to differentiate against, but the subject matter 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?

The phrase 'for common indoor conditions' implies a usage envelope and roughly matches the schema bounds (0-50 C, 1-100 %RH), but there is no explicit when-to-use/when-not-to-use statement and no mention of what to do outside that envelope. Guidance is implied rather than stated.

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.