TuneWorks

Delete object attachment

delete_object_attachment

Destructive

Delete an object attachment from blob storage after explicit confirmation.

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": {
      "fileId": "<fileId>",
      "confirmed": "<confirmed>"
    },
    "name": "delete_object_attachment"
  }
}

Input Schema

Name	Required	Description	Default
`fileId`	Yes
`confirmed`	Yes

Output Schema

Name	Required	Description
`logs`	No
`tool`	Yes	TuneWorks MCP tool name that produced this result.
`user`	No
`count`	No
`lists`	No
`setups`	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.
`sessions`	No
`vehicles`	No
`snapshots`	No
`activation`	No
`maintenance`	No
`modifications`	No
`requestedVehicleId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 24, 2026

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 / logs

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / modifications

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

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

addedOutput schema / properties / requestedVehicleId
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / snapshots

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

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

B3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds the meaningful detail that removal happens in blob storage and that a confirmation step gates the call, but it does not say whether deletion is permanent, what happens if confirmation is withheld, or whether authorization is required for open-world access.

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 with no filler; the confirmation precondition is placed before any caveats. It is appropriately sized, though it is so terse that brevity shades into under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover the destructive profile, so the definition is roughly adequate. Still, for a permanent-delete tool with 0% parameter documentation, missing details on where fileId comes from and what a false confirmed does leave a real gap.

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%, so the description must carry both parameters, yet it only obliquely explains confirmed ("explicit confirmation") and says nothing about fileId — not its source, format, or how to obtain one (presumably from list_object_attachments). This leaves the caller guessing on the key 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?

States a specific verb and resource ("Delete an object attachment") and adds the storage location ("from blob storage"), which clearly separates it from list_object_attachments and other non-delete siblings. It stops short of differentiating it from the many other delete_* tools beyond the resource name, but the resource itself is unambiguous.

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?

"After explicit confirmation" implies a precondition but merely restates the confirmed parameter rather than telling the agent when to use this tool versus alternatives. There is no statement of when deletion is appropriate, no warning about irreversibility, and no routing to sibling tools.

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?