Skip to main content
Glama

Update user preferences

update_user_preferences
Destructive

Update selected preferences for the connected TuneWorks 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": {
      "preferences": "<preferences>"
    },
    "name": "update_user_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
preferencesYes

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

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the agent already knows this is a mutating, potentially destructive write. The description adds nothing beyond that: it doesn't say whether omitted preferences are preserved or reset, whether unknown keys are rejected, or what 'selected' means operationally. For a destructive write with a free-form payload, this is a meaningful gap.

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?

One short, front-loaded sentence with no waste, but the brevity here reflects under-specification rather than disciplined conciseness — nothing about the risky free-form payload is addressed.

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. But given a nested, unconstrained preferences object and a destructiveHint=true mutation, the description omits the information an agent most needs: which keys are valid and whether the update is a merge or a replace.

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?

The single parameter is a free-form object with additionalProperties=true and 0% schema description coverage, so the schema conveys nothing about valid keys or value types. The only hint is the word "selected," which does not tell the agent which preference keys exist or what values they take. The description fails to compensate for the coverage gap.

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?

States a clear verb and resource ("Update ... preferences for the connected TuneWorks user"), so the agent knows it mutates the current user's settings. However, "selected preferences" is vague and the description does nothing to distinguish it from siblings like update_unit_settings or get_user_settings, which plausibly overlap in scope.

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 guidance on when to use this versus get_user_settings (for reading) or update_unit_settings (a specific preference category). No prerequisites, no mention that the user must be authenticated, and no exclusions.

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