TuneWorks

List custom tracks

list_custom_tracks

Read-only

List custom tracks accessible to the connected user.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_custom_tracks"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No

Output Schema

Name	Required	Description
`logs`	No
`tool`	Yes	TuneWorks MCP tool name that produced this result.
`user`	No
`count`	No
`lists`	No
`setups`	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.
`sessions`	No
`vehicles`	No
`snapshots`	No
`activation`	No
`maintenance`	No
`modifications`	No
`requestedVehicleId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 24, 2026

addedOutput schema / properties / activation

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "goal": {
+      "const": "optimize_vehicle",
+      "type": "string"
+    },
+    "missingData": {
+      "items": {
+        "enum": [
+          "vehicle",
+          "accessible_vehicle_id",
+          "baseline_setup",
+          "driving_session",
+          "vehicle_build_state",
+          "vehicle_logs",
+          "structured_vehicle_modifications"
+        ],
+        "type": "string"
+      },
+      "type": "array",
+      "uniqueItems": true
+    },
+    "nextActions": {
+      "items": {
+        "oneOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "arguments": {
+                "additionalProperties": false,
+                "properties": {
+                  "vehicleId": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "vehicleId"
+                ],
+                "type": "object"
+              },
+              "optional": {
+                "type": "boolean"
+              },
+              "reason": {
+                "type": "string"
+              },
+              "requiredInputs": {
+                "items": {
+                  "enum": [
+                    "year",
+                    "make",
+                    "model",
+                    "purpose",
+                    "displacement",
+                    "engineType",
+                    "aspiration",
+                    "cylindersOrRotors",
+                    "fuel",
+                    "fuelRating",
+                    "setupName",
+                    "setupDate",
+                    "sessionDate",
+                    "sessionFormat",
+                    "modifications",
+                    "category",
+                    "system",
+                    "status",
+                    "brand",
+                    "partName"
+                  ],
+                  "type": "string"
+                },
+                "type": "array",
+                "uniqueItems": true
+              },
+              "tool": {
+                "enum": [
+                  "create_vehicle",
+                  "list_vehicles",
+                  "get_vehicle_context",
+                  "create_setup",
+                  "create_session",
+                  "update_vehicle",
+                  "create_vehicle_modification"
+                ],
+                "type": "string"
+              },
+              "type": {
+                "const": "tool",
+                "type": "string"
+              }
+            },
+            "required": [
+              "type",
+              "tool",
+              "reason"
+            ],
+            "type": "object"
+          },
+          {
+            "additionalProperties": false,
+            "properties": {
+              "action": {
+                "enum": [
+                  "select_vehicle",
+                  "optimize_vehicle"
+                ],
+                "type": "string"
+              },
+              "optional": {
+                "type": "boolean"
+              },
+              "reason": {
+                "type": "string"
+              },
+              "type": {
+                "const": "assistant",
+                "type": "string"
+              }
+            },
+            "required": [
+              "type",
+              "action",
+              "reason"
+            ],
+            "type": "object"
+          }
+        ]
+      },
+      "type": "array"
+    },
+    "recommendedData": {
+      "items": {
+        "enum": [
+          "vehicle",
+          "accessible_vehicle_id",
+          "baseline_setup",
+          "driving_session",
+          "vehicle_build_state",
+          "vehicle_logs",
+          "structured_vehicle_modifications"
+        ],
+        "type": "string"
+      },
+      "type": "array",
+      "uniqueItems": true
+    },
+    "requestedVehicleId": {
+      "type": "string"
+    },
+    "stage": {
+      "enum": [
+        "empty_garage",
+        "select_vehicle",
+        "vehicle_selected",
+        "vehicle_created",
+        "collecting_baseline_data",
+        "ready_to_optimize"
+      ],
+      "type": "string"
+    },
+    "vehicleId": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "goal",
+    "stage",
+    "missingData",
+    "recommendedData",
+    "nextActions"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / logs

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / modifications

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

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"
+}

addedOutput schema / properties / requestedVehicleId
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / snapshots

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

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

Behavior2/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 safety is covered. The description contributes only the "accessible to the connected user" visibility note; it says nothing about pagination, default ordering, default limit behavior, or whether results are empty for users with no tracks.

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?

A single front-loaded sentence with no filler. It is efficient, but the brevity here is under-specification rather than discipline.

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-value shape need not be explained. However, for a tool with two undocumented parameters and no usage guidance relative to a large sibling set, the description leaves an agent unable to invoke `query` correctly or to decide between listing and fetching.

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% for both parameters, so the description carries the full burden of explaining `limit` (max 100, no stated default) and `query` (what field is matched — name? description? tags?). It adds nothing beyond the unannotated property names, leaving the search semantics of `query` completely undefined.

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?

The description states a verb and resource ("List custom tracks") but largely restates the name and title. The only added information is the scope qualifier "accessible to the connected user," which hints at a per-user visibility filter but does not distinguish this from get_custom_track or explain how results differ from that sibling.

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 guidance on when to use this versus get_custom_track (single-item lookup) or the create/update/delete custom track siblings. The agent must infer that this is the enumeration entry point purely from the verb "List."

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?