Skip to main content
Glama
paint-line-toolkit

paint-line-toolkit

oven_dwell_check

Calculate cure-oven dwell from conveyor path length and line speed, then verify it meets required heat-up plus time at temperature.

Instructions

Cure-oven dwell = path length ÷ line speed, checked against heat-up + time at temperature.

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": {
      "path_length_ft": "<path_length_ft>",
      "line_speed_fpm": "<line_speed_fpm>",
      "cure_time_at_temp_min": "<cure_time_at_temp_min>",
      "heat_up_min": "<heat_up_min>"
    },
    "name": "oven_dwell_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
heat_up_minYesTime for the part to reach metal temperature.
line_speed_fpmYes
path_length_ftYesConveyor length inside the heated zone.
cure_time_at_temp_minYesCure time at metal temperature.

Output Schema

NameRequiredDescriptionDefault
warningsNo
dwell_minYes
margin_minYes
assumptionsNo
heat_up_minYes
path_length_mYes
line_speed_fpmYes
meets_scheduleYes
path_length_ftYes
required_dwell_minYes
line_speed_m_per_minYes
cure_time_at_temp_minYes
required_path_length_ftYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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 it says nothing about read-only vs mutating behavior, side effects, or assumptions. The formula implies a pure calculation, but that is inference rather than disclosure; for an unannotated tool this is a meaningful gap, though not a contradiction since nothing in the text conflicts with any annotation.

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 compact sentence with no filler, front-loading the defining equation. It is borderline too terse — the operand for the comparison and the tool's output are left implicit — but nothing in it is wasted.

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 not be explained, and the four required parameters are largely documented. What is missing is the decision rule: what constitutes a pass, whether heat-up and cure time are summed as a requirement or a margin, and unit expectations. For a formula-driven check tool that is a moderate but real gap.

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

Parameters3/5

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

Schema coverage is 75% and the description goes beyond the schema by showing all four inputs in relation to each other: path_length_ft divided by line_speed_fpm yields dwell, compared against heat_up_min plus cure_time_at_temp_min. That relational meaning is genuinely useful, but the description adds no unit conventions, tolerance, or sign/pass criteria for the comparison, so it sits at the baseline for a well-covered schema.

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 the core computation (dwell = path length ÷ line speed) and implies a comparison against heat-up plus time at temperature, so the resource/purpose is inferable. But it never states a verb or the deliverable — whether this returns a numeric dwell, a pass/fail verdict, or a margin — and it draws no line between itself and siblings like conveyor_required_speed or oven_heat_load.

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 explicit when-to-use guidance, no prerequisites, and no named alternative. An agent must infer from the formula alone that this tool is for checking an existing conveyor/oven configuration rather than sizing one, which is exactly the ambiguity the sibling sizing tools create.

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