Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

suggest_design_basis

Request a design basis from an installed SizingAdvisor plug-in for paint-line sizing; when no basis is included, ask the user for the required design values.

Instructions

Ask an installed SizingAdvisor plug-in for a design basis. The public package ships none, so this normally fails with 'not included': then ask the user for the design values.

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": {
      "request": "<request>"
    },
    "name": "suggest_design_basis"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault
sourceNoWho supplied these values: 'user', an advisor name, or a note such as 'example'.user
buildingNo
booth_typeYes
heat_up_minYesTime for the part to reach metal temperature.
oven_wall_uYesPanel U-value incl. bridging, BTU/h·ft²·°F.
part_gap_ftYesClear gap between parts along the line.
elevation_ftNoSite elevation.
booth_openingNo
amu_burner_typeYes
oven_air_temp_fYesOven air setpoint.
hanger_weight_lbYesHanger/rack weight per part.
amu_supply_temp_fYes
carrier_rating_lbYesManufacturer's rated load per carrier.
oven_exhaust_scfmNoOven exhaust (vendor NFPA 86 value).
booth_velocity_fpmYesDesign velocity (liquid: OSHA Table G-10; powder: vendor).
loading_efficiencyYesFraction of carriers loaded.
oven_design_marginYesMultiplier on the oven heat balance (1.0 = none).
oven_ambient_temp_fYesTemperature around the oven / of exhaust make-up air.
oven_entering_temp_fYesTemperature of parts entering the oven.
solvent_gal_per_hourNoAlternative to oven_exhaust_scfm: NFPA 86 10,000 scf/gal screen.
amu_burner_efficiencyYes
carrier_design_factorYesMultiplier on carrier load (1.0 = none).
design_outdoor_temp_fYesWinter heating design dry-bulb (ASHRAE climatic data).
booth_control_area_ft2YesFace (crossdraft/open face), plan (downdraft) or total open area (enclosed).
chain_weight_lb_per_ftYesChain + trolleys, from the conveyor catalog.
oven_burner_efficiencyYes
oven_envelope_area_ft2YesInsulated envelope area, from the oven layout.
booth_exhausts_outdoorsYesFalse if the booth returns filtered air to the plant.
booth_extra_openings_ft2YesOther openings drawing air (e.g. silhouettes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 burden, and it does disclose the critical trait: the call is plug-in dependent and usually fails. It says nothing about what success returns, whether it is read-only or mutating, or what a plug-in install changes, so the failure profile is covered but the rest of the behavior is not.

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?

Two short sentences, front-loaded with the action and immediately followed by the failure caveat and fallback. There is no filler, though 'The public package ships none' is elliptical enough to require a second read to parse.

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 values need not be explained, and the nested request schema is richly annotated with units and constraints. The description covers the main trap (it will likely fail) but leaves the meaning of 'design basis' and what the agent should do with a successful result unstated.

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?

Top-level schema description coverage is 0% and the description adds nothing about the single `request` parameter, not even that it is a nested sizing payload or that units are imperial. The nested $defs do document individual fields, but the description does not compensate for the uncovered top-level parameter as the rubric requires at low coverage.

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 and resource: ask an installed SizingAdvisor plug-in for a design basis. That is clearly distinct from computational siblings such as size_line or amu_sizing, though it never names an alternative to confirm the distinction. What a 'design basis' actually contains is left undefined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It supplies concrete conditional guidance: in the public package the call normally fails with 'not included', and the agent should then ask the user for the design values. That is a genuine when/when-not rule rather than vague context. It stops short of routing the agent to any sibling tool for the actual sizing work.

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