Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

nfpa86_solvent_ventilation

Calculate NFPA 86 oven safety ventilation requirements by converting solvent gallons per hour into scfm using the 10,000 scf per gallon screening value.

Instructions

NFPA 86 screening value for oven safety ventilation: 10,000 scf per gallon of solvent, in scfm.

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": {
      "solvent_gal_per_h": "<solvent_gal_per_h>"
    },
    "name": "nfpa86_solvent_ventilation"
  }
}

Input Schema

NameRequiredDescriptionDefault
solvent_gal_per_hYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the exact 10,000 scf/gal rule, the input basis (per gallon of solvent), and the output units (scfm). As a pure read-only calculation there is little else to disclose, though guidance on peak vs. average solvent rates or safety factors is absent.

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?

A single sentence that front-loads the standard reference, the constant, and the units, with no filler whatsoever.

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?

An output schema exists, so return-format explanation is not needed, and the single parameter's role is implied by the factor and units. The only meaningful gap is whether the solvent rate should be a peak or time-averaged value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry meaning, and it does: it establishes that the input is a solvent quantity basis (gallons of solvent per hour) and that the result is a volumetric flow in scfm. This clarifies the rate-vs-total interpretation that the bare parameter name leaves ambiguous.

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 names a specific calculation (NFPA 86 screening value for oven safety ventilation) with the exact constant and output unit, so an agent knows precisely what it computes. It does not explicitly distinguish itself from related siblings such as oven_heat_load, which keeps it short of 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "screening value" implies preliminary sizing rather than a final design calculation, giving an agent a usable context cue. However, there is no explicit statement of when to use this versus alternatives like oven_heat_load or suggest_design_basis, and no exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.