TuneWorks

Analyze tire temperatures

analyze_tire_temperatures

Read-only

Interprets inside, middle, and outside tire temperature readings without authentication or access to TuneWorks account data.

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": {
      "readings": "<readings>"
    },
    "name": "analyze_tire_temperatures"
  }
}

Input Schema

Name	Required	Description	Default
`unit`	No		f
`readings`	Yes	Tire readings keyed by lf/rf/lr/rr, each with inside, middle, and outside numbers.
`targetTemp`	No
`tempWindow`	No
`rearCamberSpread`	No
`frontCamberSpread`	No

Output Schema

Name	Required	Description
`url`	No
`tool`	Yes	TuneWorks MCP tool name that produced this result.
`unit`	No
`tires`	No
`status`	Yes	Stable result status such as ok, created, updated, sent, auth_required, or confirmation_required.
`balance`	No
`outcome`	No	Optional domain outcome for an otherwise successful read.
`nextTest`	No
`rearAverage`	No
`frontAverage`	No
`acquisitionScope`	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

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false; the description's one added fact is that no TuneWorks authentication or account data is required, which is genuinely useful beyond the structured hints. It does not disclose what the interpretation actually produces (camber/pressure conclusions) or how the threshold parameters change the output.

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?

One front-loaded sentence with no filler or redundancy. It is under-specified rather than bloated, which is a completeness problem, not a verbosity one.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter analytical tool with nested objects, five undocumented parameters, and no explanation of the interpretation method, the definition is far too thin. An output schema exists so return values need not be described, but the agent still cannot predict how the thresholds and camber spreads affect results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%, so the description carries the burden of explaining the six parameters — yet it explains none of them. targetTemp, tempWindow, frontCamberSpread, rearCamberSpread, and unit are left entirely undocumented, and the readings object is only echoed from 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?

States a specific verb (interprets) and resource (inside/middle/outside tire temperature readings), which is more precise than the title alone. It does not distinguish itself from nearby siblings such as calculate_tire_pressure_adjustment or diagnose_handling_issue, so an agent cannot tell from the text which analysis path to pick.

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 reach for this tool, what inputs it expects, or which sibling to use instead for pressure vs. handling diagnostics. The only usage-adjacent signal is the no-auth remark, which is a constraint rather than guidance.

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?