TuneWorks

Brake Bias Calculator

calculate_brake_bias

Read-only

Estimate front brake bias from piston area, rotor size, and pad friction. Calculates from measured inputs without authentication and does not read or save account data. This estimates mechanical bias. Tire grip, weight transfer, ABS, and balance bars still 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": {
      "frontPiston": "<frontPiston>",
      "rearPiston": "<rearPiston>",
      "frontRotor": "<frontRotor>",
      "rearRotor": "<rearRotor>",
      "frontMu": "<frontMu>",
      "rearMu": "<rearMu>",
      "unitSystem": "<unitSystem>"
    },
    "name": "calculate_brake_bias"
  }
}

Input Schema

Name	Required	Description
`rearMu`	Yes	Rear pad friction
`frontMu`	Yes	Front pad friction
`rearRotor`	Yes	Rear effective radius (in in imperial; mm in metric)
`frontRotor`	Yes	Front effective radius (in in imperial; mm in metric)
`rearPiston`	Yes	Rear total piston area (in2 in imperial; cm2 in metric)
`unitSystem`	Yes	Units for all inputs and results, as specified on each field.
`frontPiston`	Yes	Front total piston area (in2 in imperial; cm2 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

A4/5.0

Behavior4/5

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

Annotations already cover readOnly/non-destructive/closed-world, but the description adds genuinely new behavioral facts: no authentication required and no account data is read or saved. It also discloses a scope limitation (purely mechanical bias), which prevents over-trusting the output. It stops short of describing determinism or precision/rounding behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: purpose first, then operational properties, then limitations. No repetition of the title and no filler; every clause adds a distinct fact.

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?

With an output schema present, return values need no explanation, and the description covers what the tool computes, its data-access profile, and its modeling limits. The only minor gap is any note on input consistency (e.g., both axles in the same unit system), which the per-field schema largely handles.

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 100%, with units and semantics documented per field, so the schema carries the parameter burden. The description only echoes the categories of input (piston area, rotor size, pad friction) and says nothing about unit-system interaction or the exclusiveMinimum>0 constraints beyond what the schema states, so baseline 3 applies.

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 ('Estimate') plus a precise resource ('front brake bias') and names the exact inputs that determine it (piston area, rotor size, pad friction). This cleanly separates it from siblings such as calculate_corner_balance or diagnose_handling_issue without needing to open 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 Guidelines3/5

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

The description implies when the result is appropriate by listing what it does not model ('Tire grip, weight transfer, ABS, and balance bars still matter'), which hints the agent should reach for a handling/diagnostic sibling in those cases. However, it never explicitly names an alternative or states a when-not-to-use condition, leaving routing to inference.

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?