Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

hook_load_check

Calculate carrier load by multiplying combined part and hanger weight by parts per carrier and design factor, then compare the result with rated capacity.

Instructions

Carrier check: (part + hanger) × parts per carrier × design factor vs rated load.

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_weight_lb": "<part_weight_lb>",
      "hanger_weight_lb": "<hanger_weight_lb>",
      "rated_capacity_lb": "<rated_capacity_lb>"
    },
    "name": "hook_load_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
spacing_ftNo
design_factorNo
part_weight_lbYes
hanger_weight_lbYes
parts_per_carrierNo
rated_capacity_lbYes

Output Schema

NameRequiredDescriptionDefault
passesYes
warningsNo
assumptionsNo
utilizationYes
design_load_lbYes
rated_capacity_lbYes
line_load_lb_per_ftYes
load_per_carrier_kgYes
load_per_carrier_lbYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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 behavioral burden. It usefully discloses the exact calculation basis, including that design_factor multiplies the load rather than the capacity, which is real behavioral information. However, it says nothing about what the check produces (margin, utilization ratio, boolean), and since an output schema exists that gap is partially mitigated but the direction of the verdict 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.

Conciseness4/5

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

A single front-loaded sentence with no filler. The formula notation is compact and readable, though the parentheses-and-'vs' syntax is slightly ambiguous about which side of the comparison is the computed value.

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?

With six parameters, zero schema description coverage, no annotations, and an output schema present, the definition is thinner than the tool's complexity warrants. It handles the core arithmetic but omits spacing_ft entirely and gives no units, defaults, or interpretation of the verdict. The presence of an output schema excuses it from describing return values, which keeps this from being a 2.

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%, so the description must compensate for all six parameters. It covers five of them (part weight, hanger weight, parts per carrier, design factor, rated capacity) and even conveys their arithmetic relationship, which is valuable. But spacing_ft is never mentioned, leaving its role in the calculation entirely unexplained, and no units or boundary behavior (e.g., null spacing) are clarified.

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 description gives a concrete formula — carrier load equals (part + hanger) weight times parts per carrier times design factor, compared against rated load — so the computation is identifiable. But it never states the outcome in plain terms (a pass/fail versus-capacity check), and the phrase 'Carrier check' is terse enough that an agent must infer that this is a load-vs-rated-capacity verification. It differentiates reasonably from siblings like oven_heat_load or conveyor_throughput by being weight/capacity focused, but only implicitly.

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 use this tool, no prerequisites (e.g., that rated capacity comes from the carrier/hook spec), and no mention of related checks such as part_clearance_check or building_clearance_check that an agent might pair it with. The agent must infer usage from the formula alone.

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