TuneWorks

Get TuneWorks app capabilities

get_tuneworks_app_capabilities

Read-only

Describes TuneWorks free public capabilities and connected garage capabilities for vehicles, setups, sessions, maintenance, shop lists, Share Build, and log history.

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": "get_tuneworks_app_capabilities"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`tool`	No	TuneWorks MCP tool name that produced this result.
`status`	No	Stable result status such as ok, created, updated, sent, auth_required, or confirmation_required.
`outcome`	No	Optional domain outcome for an otherwise successful read.
`product`	Yes
`nextStep`	No
`actionTools`	No
`publicScope`	Yes
`activationFlow`	No
`allowedObjects`	No
`authenticatedScope`	Yes
`capabilityBlockers`	No
`unavailableObjects`	No
`requiresAuthenticationForAppData`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 24, 2026

addedOutput schema / properties / actionTools / items / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / actionTools / items / properties

Added value: +{
+  "name": {
+    "type": "string"
+  },
+  "reason": {
+    "type": "string"
+  },
+  "requiresExplicitConfirmation": {
+    "type": "boolean"
+  }
+}

addedOutput schema / properties / actionTools / items / required

Added value: +[
+  "name",
+  "reason",
+  "requiresExplicitConfirmation"
+]

addedOutput schema / properties / activationFlow

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "actionTools": {
+        "items": {
+          "enum": [
+            "create_vehicle",
+            "list_vehicles",
+            "get_vehicle_context",
+            "create_setup",
+            "create_session",
+            "update_vehicle",
+            "create_vehicle_modification"
+          ],
+          "type": "string"
+        },
+        "type": "array",
+        "uniqueItems": true
+      },
+      "outcome": {
+        "type": "string"
+      },
+      "stage": {
+        "enum": [
+          "empty_garage",
+          "vehicle_created",
+          "collecting_baseline_data",
+          "ready_to_optimize"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "stage",
+      "outcome",
+      "actionTools"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / capabilityBlockers / items / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / capabilityBlockers / items / properties

Added value: +{
+  "capability": {
+    "type": "string"
+  },
+  "reason": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / capabilityBlockers / items / required
```
Added value: +[
+  "capability",
+  "reason",
+  "url"
+]
```
addedOutput schema / properties / nextStep / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / nextStep / properties

Added value: +{
+  "label": {
+    "type": "string"
+  },
+  "tool": {
+    "const": "get_garage_summary",
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / nextStep / required

Added value: +[
+  "label",
+  "tool",
+  "url"
+]

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.6/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 the agent knows this is a safe, offline, side-effect-free read; the description adds nothing on that axis. It also does not say whether results are static, user-scoped, or tier-gated (free vs. connected garage), which is the one behavioral nuance the title raises. With annotations and an output schema carrying much of the burden, a 3 is fair.

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 that names the tool's scope before the domain list, with no filler. The trailing enumeration is long but each item adds discriminating information about what the capability report covers.

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?

With zero params, full annotation coverage, and an output schema describing the return payload, the description is close to sufficient. The one omission is guidance that this is a good first call for discovery, which is the main reason an agent would reach for a capabilities tool instead of a sibling. Nothing else material is missing.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly does not waste words on inputs.

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 and resource: it describes TuneWorks capabilities, and enumerates the covered domains (vehicles, setups, sessions, maintenance, shop lists, Share Build, log history). That enumeration distinguishes it from every sibling, which are all single-resource CRUD or calculator tools. It falls short of 5 only because it does not frame itself as the discovery/entry-point tool an agent should consult before choosing siblings.

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?

There is no explicit when-to-use sentence, no prerequisites, and no named alternative. Usage is only implied by the word 'capabilities' and by the breadth of domains listed, which suggests this is an overview call rather than an operation on one resource. That inference is reasonable but not stated.

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?