TuneWorks

Recommend autocross damper adjustment

recommend_autocross_damper_adjustment

Read-only

Provides a bounded shock/damper adjustment recommendation 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": {
      "phase": "<phase>",
      "symptom": "<symptom>"
    },
    "name": "recommend_autocross_damper_adjustment"
  }
}

Input Schema

Name	Required	Default
`axle`	No	both
`phase`	Yes
`symptom`	Yes
`severity`	No

Output Schema

Name	Required	Description
`url`	No
`tool`	Yes	TuneWorks MCP tool name that produced this result.
`status`	Yes	Stable result status such as ok, created, updated, sent, auth_required, or confirmation_required.
`outcome`	No	Optional domain outcome for an otherwise successful read.
`nextStep`	No
`recommendation`	No	Recommended damper corner, adjustment direction, click count, reason, and validation check.
`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.6/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, so the description's 'without authentication or access to TuneWorks account data' adds genuinely useful context on auth and data scope. It leaves 'bounded' unexplained, though — the agent cannot tell whether the recommendation is clamped in magnitude, restricted to damper clicks, or limited in scope.

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

Conciseness3/5

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

One compact sentence with no filler, so it is concise. But brevity here comes at the cost of under-specification rather than economy — there is no front-loaded core behavior to build on.

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?

An output schema exists, so return format need not be explained, and annotations cover the safety profile. What is missing is what the tool actually recommends and how it differs from the diagnostic alternatives in a large sibling set — an agent has too little to decide confidently whether to call this tool at all.

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 0% across 4 parameters, so the description must carry the burden and it says nothing about phase, symptom, axle, or severity. The enum values are self-explanatory, but the default of axle='both', the 1-5 severity range, and how these inputs combine into a recommendation are all unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It states a verb and resource ('provides a bounded shock/damper adjustment recommendation'), so the general purpose is graspable. However, 'bounded' is never defined, and nothing distinguishes it from siblings like diagnose_handling_issue or calculate_corner_balance that an agent might reasonably pick for the same question.

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?

There is no statement of when to use this tool, when not to, or which sibling to prefer when unsure. The only selection-adjacent information is the no-auth note, which is about access, not usage context.

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?