Skip to main content
Glama

Room air changes per hour

bpj_eng_room_air_changes
Read-onlyIdempotent

Calculate nominal air changes per hour and minutes per air change from fresh airflow and room volume.

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": {
      "volume": "<volume>",
      "air": "<air>"
    },
    "name": "bpj_eng_room_air_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
airYes
volumeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already state that this is a safe, idempotent, read-only calculation with no open-world access. The description adds that the result is nominal and based specifically on fresh airflow and room volume, but it does not explain assumptions, formula details, or edge-case behavior.

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 definition is a single front-loaded sentence with no redundant or filler wording. It states the calculation and outputs efficiently.

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

Completeness4/5

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

For a simple two-parameter engineering calculator with rich safety annotations and no output schema, the description supplies enough to understand its inputs, outputs, and nominal nature. It stops short of documenting assumptions or formula details, but no major calling information is missing.

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 needs to clarify the two parameters. It identifies fresh airflow and room volume as the inputs, which maps to the air and volume parameters, but it does not add units, constraints, or formula details beyond what the schema titles already imply.

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, calculate, and a specific resource, nominal air changes per hour plus minutes per air change, with the input basis identified. It is clearly distinguishable from the other engineering calculators by its unique output, though it does not explicitly differentiate itself from siblings.

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?

The description explains what is calculated but gives no explicit guidance on when to use this tool, when not to use it, or which alternative calculator might be appropriate. Usage is only implied by the input/output names.

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.