Skip to main content
Glama
Sign In

TuneWorks

by io.github.chrismore
OverviewDiscussionsAdmin

Get garage summary

get_garage_summary
Read-only

Returns the connected garage, its activation stage, missing baseline data, and the next available actions toward vehicle optimization.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
urlNo
toolYesTuneWorks MCP tool name that produced this result.
userNo
statusYesStable result status such as ok, created, updated, sent, auth_required, or confirmation_required.
messageNo
outcomeNoOptional domain outcome for an otherwise successful read.
summaryNo
activationNo
onboardingNo
recentSetupsNo
recentSessionsNo
recentVehiclesNo
recentShopListsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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 / message
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / onboarding
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "initialFields": {
+      "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
+    },
+    "requiresUserConfirmation": {
+      "type": "boolean"
+    },
+    "state": {
+      "const": "empty_garage",
+      "type": "string"
+    },
+    "suggestedAction": {
+      "const": "create_vehicle",
+      "type": "string"
+    }
+  },
+  "required": [
+    "state",
+    "suggestedAction",
+    "initialFields",
+    "requiresUserConfirmation"
+  ],
+  "type": "object"
+}
    • 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."
  2. First observed

TDQS

B3.4/5.0
Behavior3/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 clear. The description adds that the payload includes activation stage, missing baseline data, and suggested next actions – useful framing of what 'summary' means. However, it does not say whether a garage can be absent/unconnected, or what the response looks like structurally beyond the output schema.

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 sentence that front-loads the resource and then lists the return payload. Every clause carries information; it is not padded. It is dense but readable, and nothing is repeated from the title.

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 parameters, a full output schema, and read-only annotations, the description only needs to convey purpose and content. It does that. The remaining gap is routing – when to call this instead of the other get_* context tools – which keeps it from a 5.

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 no parameter meaning to convey; baseline is 4. The description correctly implies the result is scoped by the connected user's garage rather than accepting an identifier.

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 names a specific verb ('Returns') and enumerates the returned content: connected garage, activation stage, missing baseline data, next available actions. This is more informative than the title alone. It doesn't distinguish itself from nearby 'context' siblings like get_vehicle_context or get_user_settings, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance, and no alternative tool is named. Given the many sibling tools in this server (vehicle context, user settings, capabilities), an agent has no explicit signal about when this summary is the right entry point.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TuneWorks toolsInspect
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