Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

booth_exhaust_airflow

Calculate paint or powder booth exhaust airflow in cfm from control area and design velocity, including booth type, coating, and extra openings.

Instructions

Booth exhaust airflow Q [cfm] = area [ft²] × velocity [fpm].

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": {
      "booth_type": "<booth_type>",
      "coating": "<coating>",
      "control_area_ft2": "<control_area_ft2>",
      "velocity_fpm": "<velocity_fpm>"
    },
    "name": "booth_exhaust_airflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
coatingYes
booth_typeYes
velocity_fpmYesDesign velocity (user / OSHA G-10 / vendor).
control_area_ft2Yescrossdraft: face length × height; open_face: face width × height; downdraft: plan length × width; enclosed: sum of all openings.
extra_openings_ft2No

Output Schema

NameRequiredDescriptionDefault
coatingYes
warningsNo
booth_typeYes
assumptionsNo
exhaust_cfmYes
exhaust_m3hYes
velocity_fpmYes
velocity_mpsYes
total_area_m2Yes
total_area_ft2Yes
control_area_ft2Yes
extra_openings_ft2Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It only states the mathematical relationship, without describing whether the tool validates inputs, enforces code-specific constraints, handles units, or has any side effects. The formula is a small behavioral hint but far from complete.

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?

The single-sentence formula is front-loaded and wastes no words. It is structurally efficient, though it may be overly terse for a tool with several parameters.

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?

The tool has five parameters, no annotations, and an output schema. The description offers only a formula, omitting any usage guidance, parameter clarification, or behavioral context, leaving the agent with significant gaps for correct invocation.

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 low (40%), so the description should compensate. It mentions 'area' and 'velocity' but does not clarify the five parameters, especially booth_type, coating, and extra_openings_ft2, leaving their meaning and role undocumented in both schema and description.

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 the calculation explicitly (Q = area × velocity) and names the resource (booth exhaust airflow) via the tool name. It is clear what the tool computes, but it does not differentiate this tool from siblings like osha_g10_velocity or nfpa86_solvent_ventilation.

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 provides no guidance on when to use this tool versus alternatives, no preconditions, and no exclusions. It is purely a formula with no usage context.

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