Oviond

Update saved section

update_asset

Update asset metadata. Only include fields you want to change.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Asset ID (from list_assets).
`name`	No	New name.
`tags`	No	New tag list (replaces current tags).
`description`	No	New description.
`is_recommended`	No	Promote this asset to the top of the default "Recommended" sort.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	The saved section as saved — id, name, description and tags.
`success`	Yes	True when the call succeeded. A failure comes back as an error result instead.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "The saved section as saved — id, name, description and tags.",
+      "type": "object"
+    },
+    "success": {
+      "description": "True when the call succeeded. A failure comes back as an error result instead.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

First observedSep 18, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false (mutation) and destructiveHint=false (non-destructive). The description adds the partial-update behavior ('Only include fields you want to change'), which is not in the annotations. However, it does not disclose any side effects or special behaviors beyond that, so it adds modest value.

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?

Two sentences with no filler. The purpose is front-loaded and the usage hint is concise. Every word earns its place.

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

Completeness4/5

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

For a simple metadata update tool, the description covers the essential purpose and the partial-update rule. The output schema exists, and the input schema documents all fields and requirements. It lacks guidance on alternatives but that is a usage-guideline gap rather than a completeness issue for this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all parameters (id, name, tags, description, is_recommended) are already explained. The description's 'Only include fields you want to change' provides a global usage note but does not add per-parameter meaning beyond the schema. Baseline 3 is appropriate.

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 clear verb ('Update') and resource ('asset metadata'), and the title 'Update saved section' aligns with the asset context. It distinguishes from siblings like create_asset and archive_asset by focusing on metadata updates, though it doesn't explicitly name an alternative.

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?

The instruction 'Only include fields you want to change' provides a partial-update guideline but offers no guidance on when to use this tool versus alternatives like create_asset, get_asset, or archive_asset. No exclusions or alternative routing are given, which is a gap given the large sibling set.

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

All Oviond 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?