Skip to main content
Glama
Sign In

agentView

by de.agentview
OverviewDiscussionsAdmin

Update Asset

update_asset
DestructiveIdempotent

Updates the name and/or description of an existing asset. The URL does not change. At least one of name or description must be provided. Requires authentication with at least content_only scope.

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

Input Schema

NameRequiredDescriptionDefault
nameNoNew filename for the asset.
asset_idYesThe asset ID to update.
descriptionNoNew description for the asset.
access_tokenNoOptional bearer token; prefer session_request_id.
session_request_idNoSession handle from create_auth_session; pass it on every authenticated call.

Output Schema

NameRequiredDescriptionDefault
urlNo
nameNo
sizeNo
asset_idNo
mime_typeNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "asset_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "mime_type": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "size": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / session_request_id
      Added value: +{
+  "description": "Session handle from create_auth_session; pass it on every authenticated call.",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / access_token / description
      Previous value: -"Optional JWT access token for authentication."New value: +"Optional bearer token; prefer session_request_id."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "assetId": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "description": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "name": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "url": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  4. Changed4 schema fields changed
    • changedOutput schema / properties / assetId / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / description / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / name / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / url / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  5. Changed7 schema fields changed
    • removedInput schema / properties / access_token / default
      Removed value: -null
    • changedInput schema / properties / access_token / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • removedInput schema / properties / description / default
      Removed value: -null
    • changedInput schema / properties / description / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • removedInput schema / properties / name / default
      Removed value: -null
    • changedInput schema / properties / name / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "assetId": {
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  6. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already convey mutation (readOnlyHint=false, destructiveHint=true) and idempotency. The description adds value by stating the URL invariant, the required input constraint, and the auth scope. It does not elaborate on the destructive overwrite behavior, but the annotations cover the safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences front-load the purpose and key constraint before moving to authentication. Every sentence earns its place and there is no filler.

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

Completeness5/5

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

For a five-parameter update tool with full schema coverage, an output schema, and safety annotations, the description supplies the remaining actionable details: required field combination, URL stability, and auth scope. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by clarifying that at least one of name/description is required even though the schema marks only asset_id as required, and by noting the URL remains unchanged. This adds meaningful semantic context for invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Updates') and resource ('existing asset'), and narrows the operation to 'name and/or description' while noting the URL does not change. This clearly distinguishes update_asset from siblings like upload_asset, get_asset, and delete_asset.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage constraints: at least one of name or description must be provided, and authentication requires at least content_only scope. It does not explicitly call out when to prefer upload_asset vs update_asset, but the scope and prerequisites are stated clearly enough for an agent to decide.

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

All agentView 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