TuneWorks

Gear Ratio Speed Calculator

calculate_gear_ratio_speed

Read-only

Check speed, RPM, and shift drop from tire size, final drive, and gear ratio. Calculates from measured inputs without authentication and does not read or save account data. Use measured tire diameter when possible. Tire growth and converter/clutch slip can move real-world numbers.

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": {
      "rpm": "<rpm>",
      "speed": "<speed>",
      "gear": "<gear>",
      "finalDrive": "<finalDrive>",
      "tireDiameter": "<tireDiameter>",
      "nextGear": "<nextGear>",
      "mode": "<mode>",
      "unitSystem": "<unitSystem>"
    },
    "name": "calculate_gear_ratio_speed"
  }
}

Input Schema

Name	Required	Description
`rpm`	Yes	Engine RPM (rpm)
`gear`	Yes	Gear ratio
`mode`	Yes	Primary answer
`speed`	Yes	Vehicle speed (mph in imperial; km/h in metric)
`nextGear`	Yes	Next gear ratio
`finalDrive`	Yes	Final drive
`unitSystem`	Yes	Units for all inputs and results, as specified on each field.
`tireDiameter`	Yes	Tire diameter (in in imperial; mm in metric)

Output Schema

Name	Required	Description
`url`	No
`note`	No
`tool`	Yes	TuneWorks MCP tool name that produced this result.
`inputs`	No
`result`	No
`status`	Yes	Stable result status such as ok, created, updated, sent, auth_required, or confirmation_required.
`message`	No
`outcome`	No	Optional domain outcome for an otherwise successful read.
`results`	No
`unitSystem`	No
`volumeUnit`	No
`authenticationRequired`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

addedOutput schema / properties / outcome

Added value: +{
+  "description": "Optional domain outcome for an otherwise successful read.",
+  "enum": [
+    "no_vehicles",
+    "vehicle_not_found",
+    "vehicle_selection_required",
+    "no_data"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / status / description

Previous value: -"Result status such as ok, created, updated, sent, auth_required, or confirmation_required."New value: +"Stable result status such as ok, created, updated, sent, auth_required, or confirmation_required."

First observedOct 18, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), and the description adds genuinely new behavioral context: it runs without authentication, touches no account data, and it warns that tire growth and converter/clutch slip cause real-world deviation from computed numbers. That caveat is the kind of nuance annotations cannot express.

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?

Four short sentences, front-loaded with the purpose, then scope, then input advice, then caveat. No filler, though the authentication/account-data sentence is somewhat boilerplate for a pure arithmetic tool.

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?

An output schema exists so return values need no explanation, and all eight required parameters are schema-documented. The remaining gap is that the description never explains the required 'mode' parameter's role in driving the primary answer, which an agent must infer from the schema alone.

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 100% and each field (rpm, speed, gear, finalDrive, tireDiameter, nextGear, mode, unitSystem) is already documented, so the schema does the heavy lifting. The only added meaning is the guidance to prefer a measured tire diameter, which is useful but narrow; the mode and unitSystem enums are left entirely to the 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 opens with a specific verb and outputs ('Check speed, RPM, and shift drop') plus the exact input drivers (tire size, final drive, gear ratio), which is enough to distinguish it from calculators like calculate_brake_bias or calculate_ethanol_blend. It does not explicitly name a sibling it is not, but the domain specificity is strong.

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?

It gives one concrete usage hint ('Use measured tire diameter when possible') and rules out account scope, but says nothing about when to choose this tool over neighboring calculators, nor how the required 'mode' enum (speed vs rpm) should be selected for a given question. Usage is implied rather than directed.

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

All TuneWorks tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?