TuneWorks

Lap Time Delta Calculator

calculate_lap_time_delta

Read-only

Compare two laps or sector sets and see the best theoretical lap. Calculates from measured inputs without authentication and does not read or save account data. Use sectors from timing, video, or data logs. Compare similar conditions before blaming setup.

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": {
      "baselineS1": "<baselineS1>",
      "baselineS2": "<baselineS2>",
      "baselineS3": "<baselineS3>",
      "newS1": "<newS1>",
      "newS2": "<newS2>",
      "newS3": "<newS3>"
    },
    "name": "calculate_lap_time_delta"
  }
}

Input Schema

Name	Required	Description
`newS1`	Yes	New sector 1 (sec)
`newS2`	Yes	New sector 2 (sec)
`newS3`	Yes	New sector 3 (sec)
`baselineS1`	Yes	Baseline sector 1 (sec)
`baselineS2`	Yes	Baseline sector 2 (sec)
`baselineS3`	Yes	Baseline sector 3 (sec)

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.7/5.0

Behavior3/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 safety is covered. The description adds that it needs no authentication and touches no account data, which is useful but largely a restatement of read-only behavior; it says nothing about computation assumptions or edge cases beyond that.

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?

Purpose is front-loaded in the first sentence and the remaining sentences are short. The closing line about blaming setup is coaching rather than tool behavior and is the one sentence that doesn't fully earn its place.

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 needn't be described, and a pure read-only calculator needs little behavioral disclosure. What's slightly missing is any hint that exactly three sectors per lap are expected and that the theoretical lap is a best-sector composite.

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% and every parameter is labeled with a unit (sec) and an exclusiveMinimum, so the schema carries the parameter burden. The description only adds that sectors can come from timing/video/logs — context, not syntax or semantics beyond the schema, 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 and resource — comparing two laps/sector sets — plus the derived output (best theoretical lap). This is clearly distinguishable from the many other calculate_* siblings such as calculate_brake_bias or calculate_gear_ratio_speed.

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?

"Use sectors from timing, video, or data logs" tells the agent acceptable input sources, and "Compare similar conditions before blaming setup" gives a soft usage caveat. However, no alternative tool is named and no condition is given for when NOT to use it, so guidance remains implied rather than explicit.

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?