TuneWorks

Race Alignment Checker

check_race_alignment

Read-only

Check camber and total toe against broad autocross and track baseline ranges. Calculates from measured inputs without authentication and does not read or save account data. This is a baseline checker, not a vehicle-specific prescription. Tire wear and driver feedback decide the next step.

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": {
      "frontCamber": "<frontCamber>",
      "rearCamber": "<rearCamber>",
      "frontToe": "<frontToe>",
      "rearToe": "<rearToe>",
      "use": "<use>",
      "unitSystem": "<unitSystem>"
    },
    "name": "check_race_alignment"
  }
}

Input Schema

Name	Required	Description
`use`	Yes	Use case
`rearToe`	Yes	Rear total toe (in in imperial; mm in metric)
`frontToe`	Yes	Front total toe (in in imperial; mm in metric)
`rearCamber`	Yes	Rear camber (deg)
`unitSystem`	Yes	Units for all inputs and results, as specified on each field.
`frontCamber`	Yes	Front camber (deg)

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 declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: no authentication required, no account data read or saved, and it is a pure calculation from measured inputs. That is useful detail an agent cannot infer from the annotations.

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?

Four short sentences, front-loaded with the action and reference ranges, then disclaimers, then the handoff advice. No sentence is filler and each adds a distinct piece of 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?

An output schema exists, so return values need no explanation, and annotations cover safety. The description supplies the key interpretive caveats (baseline-only, unit-agnostic inputs). Minor gap: it doesn't state what the check compares against per use case, but that is largely inferable.

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 all six parameters including the use and unitSystem enums are documented there, which sets the baseline at 3. The description names camber and total toe but adds no unit conventions or interpretation guidance for use/unitSystem beyond what the schema already states.

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?

States a specific verb and resource ('Check camber and total toe') plus the reference frame ('broad autocross and track baseline ranges'). It explicitly contrasts itself with 'a vehicle-specific prescription,' which separates it from siblings like diagnose_handling_issue or recommend_autocross_damper_adjustment, though it never names those siblings directly.

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?

Explicitly bounds when to rely on the result ('baseline checker, not a vehicle-specific prescription') and redirects the next step to tire wear and driver feedback. It stops short of naming concrete alternative tools, so routing is implied rather than spelled out.

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?