Skip to main content
Glama

Chain Drive

chain_drive
Read-only

Rates ANSI roller-chain drives by comparing link-plate fatigue and roller-impact limits, returning rated power, governing mode, and pass/fail for a specified pitch, sprocket, and speed.

Instructions

Rate an ANSI roller-chain drive (ASME B29.1). Rated at the lower of the link-plate-fatigue (HP1=0.004N1^1.08n1^0.9P^(3-0.07P), low speed) and roller-impact (HP2=1000KrN1^1.5P^0.8/n1^1.5, high speed) envelopes, P in inches. Give chain_pitch_mm (matching add_sprocket) OR a chain_number ("40","60",...) for pitch+Kr; strands scale by the B29.1 factor. Powers in W. Returns {rated_power_w, type1_power_w, type2_power_w, governing, strands, strand_factor, ..., power_sf?, pass}. k_r overrides the roller-impact constant the chain_number lookup supplies (29 for the 25-240 series, 17 for the lightweight #41) — needed for a chain outside the ANSI table.

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": {
      "teeth_small": "<teeth_small>",
      "speed_rpm": "<speed_rpm>"
    },
    "name": "chain_drive"
  }
}

Input Schema

NameRequiredDescriptionDefault
k_rNo
power_wNo
strandsNo
speed_rpmYes
workspaceNoRun this call in this named workspace
teeth_smallYes
chain_numberNo
chain_pitch_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the behavioral bar is lower; the description still adds real substance by disclosing the two governing envelopes, that the rating is the lower of them, that strands scale by the B29.1 factor, and by listing the returned keys including "governing" and "strand_factor". It stops short of stating failure conditions or validation behavior (e.g., invalid chain_number, missing pitch) or what "pass" means.

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?

Front-loaded with the purpose and the rating basis, then parameters, then return keys — a sensible order with no filler sentences. It is dense to the point of being cryptic (embedded formulas, a trailing k_r aside appended after the return list) but essentially every clause carries technical information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex multi-parameter engineering calculation with no output schema and low schema coverage, the description supplies the rating model, the pitch/number alternative, the strand factor, the k_r override, and the return shape. The remaining omissions (precedence between pitch and chain_number, meaning of power_sf/pass, error behavior) are the difference between good and exhaustive rather than blockers.

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 description coverage is only 13% on 8 parameters, so the description must carry the load and largely does: it explains chain_pitch_mm units and sprocket compatibility, gives concrete chain_number examples ("40","60"), documents k_r's override semantics with its two values (29 vs 17 for #41), and clarifies strands scaling and that powers are in W. Gaps remain: power_w is never explicitly defined relative to "power_sf", workspace is undocumented in the description, and precedence when both chain_pitch_mm and chain_number are supplied is unstated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "Rate an ANSI roller-chain drive (ASME B29.1)", which is unambiguous against siblings such as belt_drive, gear_rating, and add_sprocket. It also names the exact rating basis (link-plate fatigue vs roller-impact envelopes), so an agent knows precisely what computation it gets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Guidance is parameter-level ("Give chain_pitch_mm ... OR a chain_number") rather than tool-level. It never says when to reach for this instead of belt_drive/gear_rating, nor when the rating is not applicable (e.g., non-ANSI or non-chain power transmission). Usage is implied by the resource name, not stated.

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

Deploy Server

Other Tools