TuneWorks

Create team

create_team

Create a new team for the connected user.

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": {
      "name": "<name>"
    },
    "name": "create_team"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes

Output Schema

Name	Required	Description
`url`	No
`list`	No
`tool`	Yes	TuneWorks MCP tool name that produced this result.
`user`	No
`setup`	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.
`session`	No
`tracker`	No
`vehicle`	No
`activation`	No
`modification`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 24, 2026

changedOutput schema / description

Previous value: -"TuneWorks app object create/update result with the saved object and connected user."New value: +"TuneWorks app object create/update result with the saved object, connected user, and next activation actions."

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 / modification
```
Added value: +{
+  "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."

First observedOct 18, 2026

TDQS

C2.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare non-read-only, non-destructive, closed-world behavior, so the safety profile is covered. Beyond that the description adds only that the team belongs to the connected user; it says nothing about whether the caller becomes owner, whether names must be unique, how many teams a user may hold, or what happens on duplicate names.

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?

One short sentence with the verb and resource front-loaded and zero filler. It is efficient, though the brevity is under-specification rather than disciplined compression.

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 values needn't be described, and annotations cover safety. But for a mutation tool sitting among 80+ siblings with an undocumented parameter, the description should at least cover ownership semantics and name constraints; those gaps make it thin for correct invocation.

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% and the single 'name' property is an undescribed string, so the description must compensate — but it says nothing about format, length, uniqueness, or validation. An agent could pass a duplicate or malformed name with no warning.

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 ("Create a new team"), so an agent knows exactly what entity is produced. However, it offers no differentiation from the many sibling team tools (rename_team, delete_team, send_team_invite, leave_team), leaving the agent to infer the boundary from names alone.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as send_team_invite for adding people or list_teams for checking existing teams. The single clause "for the connected user" is the only contextual hint and it is about scoping, not usage selection.

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?