Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

part_clearance_check

Checks whether a hung part’s cross-section fits through a booth or oven opening while meeting the required side clearance before sizing or routing.

Instructions

Hung part cross-section vs a booth/oven silhouette or working opening.

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": {
      "part_width_ft": "<part_width_ft>",
      "part_height_ft": "<part_height_ft>",
      "opening_width_ft": "<opening_width_ft>",
      "opening_height_ft": "<opening_height_ft>",
      "min_clearance_in": "<min_clearance_in>"
    },
    "name": "part_clearance_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
part_width_ftYesAcross the direction of travel.
part_height_ftYes
min_clearance_inYesRequired clearance per side.
opening_width_ftYes
opening_height_ftYes

Output Schema

NameRequiredDescriptionDefault
passesYes
warningsNo
assumptionsNo
part_width_ftYes
part_height_ftYes
min_clearance_inYes
opening_width_ftYes
opening_height_ftYes
side_clearance_inYes
vertical_clearance_inYes
required_opening_width_ftYes
required_opening_height_ftYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/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 and largely drops it. It does not say whether the check is two-dimensional, how min_clearance_in is applied (schema says per side but not whether to both sides or one), whether the result is advisory or enforcing, or what happens when the part exceeds the opening.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no padding, so nothing is wasteful. But the brevity comes at the cost of front-loading any actionable information; an agent reading it still has to infer the verb, the comparison rule, and the result type.

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?

For a five-parameter, all-required geometric check with no annotations, the definition is far too thin. An output schema exists so return values need not be described, but the description should at least explain the geometry being checked, the direction-of-travel assumption, and how clearance margins are applied.

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?

Schema description coverage is only 40%: part_width_ft has orientation context ('across the direction of travel') and min_clearance_in states 'per side', but part_height_ft, opening_width_ft and opening_height_ft are undocumented. The description adds nothing to explain how the five dimensions combine into an envelope check, so half the parameters remain semantically bare.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment names the comparison the tool performs (hung part cross-section versus a booth/oven silhouette or working opening), which is real substance beyond the tool name. However it is a noun phrase with no verb and no statement of the outcome, so an agent cannot tell from the text alone whether it returns a pass/fail, a required dimension, or just a boolean clearance flag.

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?

There is no guidance on when to call this instead of alternatives, even though a sibling named building_clearance_check performs an adjacent clearance check and the label 'working opening' versus 'booth/oven silhouette' is never disambiguated. Nothing says when the tool does not apply or what input geometry it expects.

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