Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

conveyor_throughput

Calculate parts per hour from conveyor line speed, carrier pitch, parts per carrier, and loading efficiency to size paint line throughput.

Instructions

Parts/hour = speed × 60 ÷ pitch × parts per carrier × loading efficiency.

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": {
      "line_speed_fpm": "<line_speed_fpm>",
      "spacing_ft": "<spacing_ft>"
    },
    "name": "conveyor_throughput"
  }
}

Input Schema

NameRequiredDescriptionDefault
spacing_ftYesCarrier pitch.
line_speed_fpmYes
parts_per_carrierNo
loading_efficiencyNo

Output Schema

NameRequiredDescriptionDefault
warningsNo
spacing_mYes
spacing_ftYes
assumptionsNo
line_speed_fpmYes
parts_per_hourYes
carriers_per_hourYes
parts_per_carrierYes
loading_efficiencyYes
line_speed_m_per_minYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden. It does disclose the exact computation, which strongly implies a pure, side-effect-free calculation, but it never states that the tool is read-only/non-mutating, never notes unit conventions for the result, and says nothing about edge cases such as a zero or fractional loading efficiency.

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 formula with zero padding — every token earns its place and it is maximally compact. It loses a point because it is not front-loaded with a plain-language statement of what the tool computes, forcing the agent to parse the equation first.

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?

An output schema exists, so return values need no explanation, and the formula covers the core math for four parameters. However, for a tool with 25% schema coverage and no annotations, the description should also settle unit conventions for the result and the 0–1 vs percent question for loading_efficiency; as written those remain inferential.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25% (only 'spacing_ft' is annotated as 'Carrier pitch'), so the description must compensate, and it does: mapping 'speed' to line_speed_fpm, 'pitch' to spacing_ft, plus parts per carrier and loading efficiency, and the '× 60' implicitly confirms fpm-to-ft/hr units. It stops short of clarifying that loading_efficiency is a 0–1 fraction rather than a percentage, which is the one remaining ambiguity.

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 is a bare formula: 'Parts/hour = speed × 60 ÷ pitch × parts per carrier × loading efficiency.' An agent can infer this is a conveyor throughput calculator, but it never states the verb+resource in words ('compute conveyor throughput in parts per hour'), and it does nothing to distinguish itself from the sibling 'conveyor_required_speed', which is clearly the inverse calculation.

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 at all. The formula implies this is the forward sizing calculation versus the inverse 'conveyor_required_speed', but the description never says so, never mentions prerequisites (e.g., carrier pitch must be known), and gives no exclusions.

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