Skip to main content
Glama

Belt Drive

belt_drive
Read-only

Calculates wrap angle, belt speed, tension ratio, and transmissible power for pulley belt drives, returning tight/slack tensions and a pass/fail rating.

Instructions

Rate a belt drive (Eytelwein/capstan). Wrap theta=pi-2asin((D-d)/2C), Fe=P/V, T1/T2=e^(mu*theta) (V-belt divides mu by sin(beta/2)). Returns {wrap_angle_deg, belt_speed_m_s, effective_force_n, tension_ratio, tight_side_n, slack_side_n, transmissible_power_w, pass}.

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": {
      "power_w": "<power_w>",
      "small_pulley_dia_mm": "<small_pulley_dia_mm>",
      "large_pulley_dia_mm": "<large_pulley_dia_mm>",
      "center_distance_mm": "<center_distance_mm>",
      "small_pulley_rpm": "<small_pulley_rpm>"
    },
    "name": "belt_drive"
  }
}

Input Schema

NameRequiredDescriptionDefault
power_wYes
workspaceNoRun this call in this named workspace
friction_coefNo
small_pulley_rpmYes
vbelt_groove_degNo
center_distance_mmYes
tight_side_limit_nNo
large_pulley_dia_mmYes
small_pulley_dia_mmYes

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value by exposing the governing equations and the returned field set. However, it omits behavioral details an agent needs: what causes the 'pass' flag to be true/false, how tight_side_limit_n gates the result, and unit assumptions.

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?

Very compact and front-loaded: purpose first, then formulas, then the return contract. The math notation is dense but each clause carries information; nothing is padding, though readability for a non-domain agent is limited.

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?

There is no output schema, and the description correctly compensates by enumerating all eight return keys — a genuine strength. Still missing for a 9-parameter engineering calculation: the pass/fail criterion, the tight-side limit's role, and explicit unit conventions.

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 description coverage is only 11% across 9 parameters, so the description must carry the load; it maps most inputs via formula symbols (D/d diameters, C center distance, P power, mu friction, beta groove angle) and even explains V-belt mu division. But tight_side_limit_n and workspace are never explained, and no units are stated beyond the formula structure.

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?

Starts with a specific verb+resource: 'Rate a belt drive (Eytelwein/capstan)' and immediately grounds it in named formulas, so an agent knows this is a belt-drive rating calculation. It does not explicitly distinguish itself from siblings like chain_drive or gear_rating, which is the only thing keeping it off a 5.

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 never says when to use this tool versus alternatives (chain_drive, gear_rating, spring_check) or what preconditions/inputs it expects. It is pure formula and return-value exposition with no routing or exclusion guidance.

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