Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update home catalog settings

nuvio_update_home_catalog_settings

Modify home screen layout and catalog settings with patch, set, or unset operations. Preview changes using dry-run mode and restore a previous snapshot.

Instructions

Update the home screen layout/catalog blob with the same patch/set/unset semantics as nuvio_update_settings. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
setNoSet nested values by dot path, applied after patch.
patchNoDeep-merged into the settings tree.
unsetNoDelete nested keys by dot path, applied last.
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
platformNotv
profile_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.1.1
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Return the diff without writing anything (no snapshot, no audit entry).",
+  "type": "boolean"
+}
    • addedInput schema / properties / patch
      Added value: +{
+  "additionalProperties": {},
+  "description": "Deep-merged into the settings tree.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • removedInput schema / properties / platform / description
      Removed value: -"Platform namespace: tv | mobile | desktop | web"
    • addedInput schema / properties / set
      Added value: +{
+  "description": "Set nested values by dot path, applied after patch.",
+  "items": {
+    "properties": {
+      "path": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "value": {}
+    },
+    "required": [
+      "path",
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / settings
      Removed value: -{
-  "additionalProperties": {},
-  "propertyNames": {
-    "type": "string"
-  },
-  "type": "object"
-}
    • addedInput schema / properties / unset
      Added value: +{
+  "description": "Delete nested keys by dot path, applied last.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / required
      Removed value: -[
-  "settings"
-]
  2. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate it's not read-only (readOnlyHint=false), not destructive (destructiveHint=false), and not idempotent. The description goes beyond this by mentioning that it supports dry_run, snapshots the previous state before writing, and can be reverted via nuvio_undo. This adds valuable behavioral context about undo capability and non-destructive nature.

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?

The description is two concise sentences. The first sentence states the core functionality and aligns with a known sibling tool. The second sentence adds key behavioral details (dry_run, snapshot, revert) without fluff. Everything is front-loaded and necessary.

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?

Complexity is moderate with 6 parameters and nested objects. The description covers the core purpose and safety net (snapshot, revert), but lacks details on the platform and profile_id parameters, which the schema doesn't explain either. There is also no output schema, but a diff is likely returned; the description's mention of dry_run implies a diff but doesn't state the return format. Given the richness of the schema and the supplementary hints, it's adequate but not fully complete.

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 at 67%, with the key parameters (set, patch, unset, dry_run) having descriptions. However, platform and profile_id lack descriptions in the schema, and the tool description does not compensate for them. The description adds the semantics of patch/set/unset matching nuvio_update_settings, but doesn't clarify what platform/profile_id do. Baseline is 3 when schema covers a majority, and this is appropriate; it doesn't add much beyond the schema.

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 clearly states it updates the home screen layout/catalog blob, references the same semantics as a sibling tool (nuvio_update_settings), and implicitly distinguishes itself by targeting the home catalog specifically. This is a specific verb+resource that an agent can differentiate from the other update tools.

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 mentions the patch/set/unset semantics align with nuvio_update_settingsressions, which provides clear context for how it behaves. It also mentions the dry_run option, which implicitly guides when to use it for testing. However, it doesn't explicitly state when not to use it versus alternatives like nuvio_set_home_catalog_path, though the context is reasonably clear.

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

Deploy Server

Other Tools