Skip to main content
Glama

Update custom vehicle make

update_vehicle_make
Destructive

Rename or rescope a custom vehicle make.

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": {
      "id": "<id>",
      "make": "<make>"
    },
    "name": "update_vehicle_make"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
makeYes
teamIdNo

Output Schema

NameRequiredDescriptionDefault
urlNo
listNo
toolYesTuneWorks MCP tool name that produced this result.
userNo
setupNo
statusYesStable result status such as ok, created, updated, sent, auth_required, or confirmation_required.
messageNo
outcomeNoOptional domain outcome for an otherwise successful read.
sessionNo
trackerNo
vehicleNo
activationNo
modificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • 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."
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description contributes the useful nuance that it targets *custom* makes only, but leaves "rescope" undefined and says nothing about side effects on vehicles using the make or team-scoping rules. With annotations carrying the destruction warning, this is adequate but thin.

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?

The single sentence is front-loaded and waste-free, but at six words it is under-specified rather than efficient. Conciseness here comes at the cost of the operational detail an agent needs.

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?

For a destructive three-parameter mutation, the definition omits parameter meaning, side effects, and team/permission context. The existing output schema relieves it of explaining return values, but the remaining gaps around "rescope" and teamId are significant.

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 description explains none of the three parameters. "Rename" loosely maps to make and "rescope" may hint at teamId, but it never clarifies what teamId does or that id identifies the make record, so the agent gets no help beyond bare schema types.

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 states a specific pair of verbs ("rename or rescope") and a specific resource ("custom vehicle make"), making it clear this modifies an existing custom make rather than a global/OEM one. It does not explicitly name siblings like create_vehicle_make or delete_vehicle_make, but the verb choice implicitly separates it from those operations.

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 create_vehicle_make, delete_vehicle_make, or update_vehicle. No prerequisites (ownership, team membership, whether vehicles referencing the make are affected) are stated, leaving the agent to infer the correct context entirely.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources