Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

conveyor_required_speed

Calculates the line speed in feet per minute needed to meet a target production rate, factoring part spacing, parts per carrier, and loading efficiency for conveyor sizing.

Instructions

Line speed (fpm) required for a target production rate.

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": {
      "target_parts_per_hour": "<target_parts_per_hour>",
      "spacing_ft": "<spacing_ft>"
    },
    "name": "conveyor_required_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
spacing_ftYes
parts_per_carrierNo
loading_efficiencyNo
target_parts_per_hourYes

Output Schema

NameRequiredDescriptionDefault
warningsNo
spacing_ftYes
assumptionsNo
carriers_per_hourYes
parts_per_carrierYes
loading_efficiencyYes
required_speed_fpmYes
target_parts_per_hourYes
required_speed_m_per_minYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says what is calculated and in what units, but it does not explain the calculation assumptions, how optional parameters affect the result, or any constraints on valid inputs.

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?

The definition is a single front-loaded sentence with no wasted wording. Its brevity is efficient, though it is too terse to carry the necessary parameter and usage detail.

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?

The tool has four parameters, no annotations, and no schema descriptions, so the description needs to provide more context. It correctly states the computed quantity and units, but it leaves out parameter meanings, assumptions, and selection guidance.

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

Parameters1/5

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

Schema description coverage is 0%, and four parameters are present, but the description only implicitly references target production rate. It does not explain spacing_ft, parts_per_carrier, or loading_efficiency, so it does not compensate for the undocumented schema.

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 states the specific output, line speed in fpm, and the condition it is computed for, a target production rate. It is clear enough to distinguish this from a general throughput calculator, though it does not name a sibling alternative.

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?

The description implies when the tool is useful, but it gives no explicit usage guidance, prerequisites, or comparison to sibling sizing tools such as conveyor_throughput.

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