Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

index_cycle

Calculate indexing conveyor cycle, move, and dwell times per station from target throughput, index distance, speed, and acceleration/deceleration to size conveyor timing.

Instructions

Indexing conveyor: cycle time, move time and dwell available per station.

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>",
      "index_distance_ft": "<index_distance_ft>",
      "index_speed_fpm": "<index_speed_fpm>",
      "accel_decel_s": "<accel_decel_s>"
    },
    "name": "index_cycle"
  }
}

Input Schema

NameRequiredDescriptionDefault
accel_decel_sYes
index_speed_fpmYes
parts_per_indexNo
index_distance_ftYes
target_parts_per_hourYes

Output Schema

NameRequiredDescriptionDefault
feasibleYes
warningsNo
assumptionsNo
move_time_sYes
cycle_time_sYes
dwell_time_sYes
move_fractionYes
parts_per_indexYes
target_parts_per_hourYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior1/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 and delivers almost nothing. It never states that this is a side-effect-free calculation, what modeling assumptions govern the cycle/move/dwell split, what unit system is used, or whether results are estimates versus hard constraints. For a five-input engineering calculation with zero annotation coverage, this is a serious gap.

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?

The single sentence is front-loaded and free of padding, so nothing is wasted. The problem is under-specification rather than verbosity: the available space is not used to state the calculation verb, units, or assumptions that would make the sentence actionable.

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?

An output schema exists, so return values need not be spelled out, which is the one thing in this definition's favor. Still, a five-parameter engineering calculator with no annotations and no parameter documentation leaves the agent without enough information to supply correct inputs or know when this tool is the right choice versus its conveyor siblings.

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 coverage is 0% — parameters carry only bare titles, and the description mentions none of them. It says nothing about the meaning of target_parts_per_hour versus parts_per_index, the default of 1 on parts_per_index, or the units/significance of accel_decel_s, index_speed_fpm, and index_distance_ft. The titles are largely self-explanatory, which prevents a score of 1, but the description contributes no meaning of its own.

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 names the resource (indexing conveyor) and the outputs it produces (cycle time, move time, dwell per station), which is more than a restatement of the name. However, it is a noun-phrase fragment with no explicit verb, so an agent must infer that this computes rather than retrieves or configures anything. It also gives no signal distinguishing it from the related conveyor_throughput or conveyor_required_speed siblings.

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 statement, no prerequisites, and no mention of alternative tools. The only usage hint is implicit in the phrase 'indexing conveyor', leaving the agent to guess whether this is an early sizing pass or a verification step against other conveyor tools in the catalog.

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