TuneWorks

Tire Pressure Adjustment Calculator

calculate_tire_pressure_adjustment

Read-only

Turn cold, hot, and target hot pressures into the next cold pressure to try. Calculates from measured inputs without authentication and does not read or save account data. This gives a next-test pressure, not a universal ideal. Recheck after the next run.

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": {
      "cold": "<cold>",
      "hot": "<hot>",
      "target": "<target>",
      "ambientChange": "<ambientChange>",
      "unitSystem": "<unitSystem>"
    },
    "name": "calculate_tire_pressure_adjustment"
  }
}

Input Schema

Name	Required	Description
`hot`	Yes	Measured hot pressure (psi in imperial; bar in metric)
`cold`	Yes	Starting cold pressure (psi in imperial; bar in metric)
`target`	Yes	Target hot pressure (psi in imperial; bar in metric)
`unitSystem`	Yes	Units for all inputs and results, as specified on each field.
`ambientChange`	Yes	Expected ambient temp change (F in imperial; C 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.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context: no authentication is needed, no account data is read or saved, and the result is an experimental next-test pressure rather than a universal target.

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?

The description is short, front-loaded with the core transformation, and each sentence adds useful context. There is no redundant or filler text.

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?

The tool has an output schema and full parameter documentation, so the description does not need to explain return values or every input detail. It covers the key caveat about the result being a next-test pressure, though it could say slightly more about assumptions or expected input relationships.

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 the schema already documents all five parameters, including unitSystem and ambientChange. The description reinforces the main pressure inputs but does not add meaning beyond what the schema provides.

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 states a specific calculation: converting cold, hot, and target hot pressures into the next cold pressure to try. It is clear what the tool does, but it does not explicitly distinguish itself from nearby tire-related siblings such as analyze_tire_temperatures.

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 usage by explaining that it produces a next-test pressure rather than a universal ideal and says to recheck after the next run. However, it does not state explicit when-to-use conditions, prerequisites, or alternative tools to choose instead.

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?