Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

building_clearance_check

Checks overhead clearance between equipment and truss bottoms and verifies exhaust stack height above the roof against minimum requirements.

Instructions

Equipment top vs bottom of truss, and exhaust stack discharge height vs roof.

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": {
      "equipment_top_ft": "<equipment_top_ft>",
      "bottom_of_truss_ft": "<bottom_of_truss_ft>",
      "roof_height_ft": "<roof_height_ft>",
      "min_overhead_clearance_ft": "<min_overhead_clearance_ft>",
      "min_stack_above_roof_ft": "<min_stack_above_roof_ft>"
    },
    "name": "building_clearance_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
stack_top_ftNo
roof_height_ftYes
equipment_top_ftYes
bottom_of_truss_ftYes
min_stack_above_roof_ftYes
min_overhead_clearance_ftYes

Output Schema

NameRequiredDescriptionDefault
stack_okYes
warningsNo
assumptionsNo
roof_height_ftYes
equipment_top_ftYes
fits_under_trussYes
bottom_of_truss_ftYes
required_stack_top_mYes
overhead_clearance_ftYes
required_stack_top_ftYes
stack_height_above_roof_ftYes
required_overhead_clearance_ftYes
stack_length_above_equipment_ftYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and delivers very little. It does not say whether results are boolean pass/fail, whether margins are reported, what happens when stack_top_ft is null (an optional parameter in the schema), or what tolerances apply. The presence of an output schema relieves it of explaining return values, but the comparison logic itself remains undisclosed.

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

Conciseness2/5

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

Brevity here is under-specification rather than conciseness: a single sentence fragment with no verb and no structure. Nothing is wasted, but nothing is front-loaded beyond two bare comparison phrases, leaving the agent to reconstruct the tool's contract.

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 six-parameter tool with five required inputs, no annotations, and 0% schema coverage, this is far too thin. The output schema covers return values, but the description never explains the two minimum-threshold inputs, null handling for stack_top_ft, or units, so an agent cannot confidently parameterize the call.

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 0% across six parameters, so the description must compensate and largely fails to. It loosely maps to equipment_top_ft, bottom_of_truss_ft, roof_height_ft and implicitly stack_top_ft, but never mentions min_overhead_clearance_ft or min_stack_above_roof_ft — the two threshold parameters that determine the verdict — nor any units or expected magnitude.

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 two concrete comparisons — equipment top vs bottom of truss, and stack discharge height vs roof — which tells an agent the resource domain. But it is a noun phrase, not a statement of what the tool does: there is no verb saying it verifies, returns pass/fail, or reports a margin. It also does not distinguish itself from sibling clearance checks such as part_clearance_check.

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 when-to-use guidance, no prerequisites, and no routing to alternatives. An agent must infer from the name alone that this is for building/structural clearance rather than part clearance or hook load. The description neither states exclusions nor names a sibling.

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