Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

osha_g10_velocity

Calculate the minimum maintained air velocity required for liquid spray booths under OSHA 29 CFR 1910.94(c)(6) Table G-10; for powder booths, request the vendor's specified value.

Instructions

Minimum maintained air velocity into a liquid spray booth, from OSHA 29 CFR 1910.94(c)(6) Table G-10. There is no public table for powder booths: ask the user for the vendor's value.

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": {
      "condition": "<condition>",
      "booth_size": "<booth_size>"
    },
    "name": "osha_g10_velocity"
  }
}

Input Schema

NameRequiredDescriptionDefault
conditionYes
booth_sizeYes

Output Schema

NameRequiredDescriptionDefault
noteYes
sourceYes
max_fpmYes
min_fpmYes
conditionYes
booth_sizeYes
design_fpmYesDesign velocity, fpm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full load; it does disclose that the value is a regulatory minimum and comes from a fixed table, which is useful. It omits units (fpm), whether the returned value is a single number or a table slice, and any note that the figure is a floor rather than a design target — though an output schema exists, units are still an input-side expectation the description should set.

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?

Two sentences, zero filler: the positive scope is front-loaded and the exception follows immediately. Every sentence carries information an agent needs.

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?

The output schema means return values need not be explained, and the regulatory source plus the powder-booth caveat cover the core. However, for a lookup tool whose whole value is a precise number, the absence of units and of any definition for the large/small booth split leaves meaningful gaps.

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?

The description never mentions the two required parameters, and reported schema description coverage is 0%. The 'condition' enum values are self-explanatory, but 'booth_size' of 'large' vs 'small' has undefined thresholds in Table G-10, and the description does nothing to clarify them, leaving a real semantic gap.

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 the specific quantity (minimum maintained air velocity), the target (liquid spray booth), and the exact regulatory source (OSHA 29 CFR 1910.94(c)(6) Table G-10), so an agent knows this is a table lookup rather than a calculation. It does not explicitly distinguish itself from siblings such as booth_exhaust_airflow, but the regulatory-table framing makes the boundary inferable.

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?

It gives a clear negative case and fallback: for powder booths there is no public table, so the agent should ask the user for the vendor's value. That is genuine routing guidance, but there is no statement of when to prefer this tool over related airflow/ventilation siblings, so usage is only partially covered.

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