Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

size_line

Performs preliminary sizing of a complete paint finishing line—conveyor, booth, oven, make-up air unit and clearances—using a production request and complete design basis.

Instructions

Preliminary sizing of a whole finishing line (conveyor, booth, oven, AMU, clearances). Needs the sizing request AND a complete design basis; ask the user for any value you lack.

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": {
      "spec": "<spec>"
    },
    "name": "size_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes

Output Schema

NameRequiredDescriptionDefault
amuYes
specYes
boothYes
summaryYes
buildingYes
conveyorYes
warningsYes
hook_loadYes
disclaimerNoPreliminary sizing aid only. This toolkit implements public, textbook and code-cited relationships; every design value (velocities, margins, efficiencies, allowances, geometry) is supplied by the user. Results are NOT a substitute for equipment-vendor engineering, a licensed engineer's design, or review by the authority having jurisdiction (AHJ) against the code editions in force (e.g. NFPA 33, NFPA 86, OSHA 29 CFR 1910.94/1910.107, local fire and gas codes).
oven_dwellYes
assumptionsYes
booth_openingYes
oven_heat_loadYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully flags that results are 'preliminary' and that incomplete inputs are expected to be resolved by asking the user, but it never states that this is a side-effect-free calculation, nor what happens if the design basis is partial or a clearance check fails.

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, front-loaded with the scope and followed immediately by the input precondition. Nothing is repeated from the schema and no sentence is wasted.

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 whole-line sizing tool with a rich nested schema and an output schema, the description covers what it computes and what it requires, which is most of what an agent needs. The main residual gap is that it never says how the whole-line result relates to the per-component tools an agent might otherwise call first.

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?

There is a single top-level parameter (spec) wrapping SizingRequest and DesignBasis, and the description does name both halves and stress that the basis must be complete with no defaults. It adds no further mapping of what belongs in each half or the imperial unit convention, leaving the nested schema to do that work.

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 gives a specific verb ('Preliminary sizing') and a specific resource ('a whole finishing line'), then enumerates the subsystems covered (conveyor, booth, oven, AMU, clearances). That scope enumeration implicitly separates it from the single-component siblings, but it never names or explicitly contrasts with any of them.

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 states a real precondition ('Needs the sizing request AND a complete design basis') and a fallback ('ask the user for any value you lack'), which is useful context for invoking it. However, there is no when-to-use versus when-not guidance relative to the granular sibling tools (oven_heat_load, booth_exhaust_airflow, amu_sizing), and no note on what to do if only part of the line is in scope.

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