TuneWorks

Corner Balance Calculator

calculate_corner_balance

Read-only

Calculate cross weight, left/right balance, and front/rear split from four scale pads. Calculates from measured inputs without authentication and does not read or save account data. Measure the car in the same state you drive it: driver, fuel, ballast, and tire pressures matter.

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": {
      "lf": "<lf>",
      "rf": "<rf>",
      "lr": "<lr>",
      "rr": "<rr>",
      "unitSystem": "<unitSystem>"
    },
    "name": "calculate_corner_balance"
  }
}

Input Schema

Name	Required	Description
`lf`	Yes	Left front (lb in imperial; kg in metric)
`lr`	Yes	Left rear (lb in imperial; kg in metric)
`rf`	Yes	Right front (lb in imperial; kg in metric)
`rr`	Yes	Right rear (lb in imperial; kg in metric)
`unitSystem`	Yes	Units for all inputs and results, as specified on each field.

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

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-schema behavior: no authentication, no account data read or written, and the measurement-state precondition that affects result validity.

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?

Three sentences, front-loaded with the core capability, then side-effect disclosure, then the measurement precondition. Every sentence carries information, though the middle sentence slightly overlaps with what the read-only annotations already convey.

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 not be explained, and annotations cover the safety profile. The description supplies the auth/data-access behavior and input preconditions an agent needs, leaving only minor gaps like input ordering or unit consistency reminders.

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%, so each pad and the unitSystem enum are already fully documented, establishing the baseline of 3. The description adds only the 'four scale pads' framing and a reminder that measurement conditions matter, which is helpful but does not add per-parameter detail beyond the schema.

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 ('Calculate') and the exact outputs (cross weight, left/right balance, front/rear split) plus the input source (four scale pads). This clearly separates it from sibling calculators such as calculate_brake_bias or calculate_spring_wheel_rate without opening any schema.

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

Usage Guidelines4/5

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

Gives a clear usage context ('Calculates from measured inputs without authentication and does not read or save account data') and even a precondition ('measure the car in the same state you drive it'). It stops short of naming when to prefer a sibling tool or when not to use it, so it falls just below the explicit-alternatives bar.

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?