Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update profile settings

nuvio_update_settings

Update a profile's settings blob with deep-merge patches, dot-path set/unset operations, dry-run previews, and undoable snapshots.

Instructions

Update a profile settings blob. patch is deep-merged (nested keys are preserved, arrays and scalars replace), set assigns nested dot paths and unset deletes them — applied in the order patch, set, unset. This is the canonical replacement for nuvio_set_setting / nuvio_unset_setting. 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.6/5.0
Behavior5/5

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

Annotations only indicate readOnlyHint=false and do not convey semantic nuance. The description adds substantial behavioral detail: deep-merge rules for patch, assignment/deletion semantics for set/unset, application order, snapshotting before write, undo support, and dry_run's explicit no-write/no-snapshot/no-audit behavior.

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 dense sentences cover the core action, merge semantics, ordering, replacement of older tools, dry-run capability, and revert path. Every clause carries operational weight, and the most important behavior is front-loaded.

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 mutating settings tool with no output schema, the description gives enough to call correctly: merge rules, order, dry-run effects, snapshot/undo behavior, and deprecation guidance. The only notable gap is the lack of an explicit statement about the normal response shape or return value.

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 67%, with platform and profile_id lacking descriptions. The description compensates by explaining how patch, set, and unset actually behave and in what order, which is more valuable than the schema's brief phrases. It does not add detail for platform/profile_id, but their defaults and constraints are already in 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?

States a specific verb and resource: 'Update a profile settings blob,' then details the exact operation modes (patch/set/unset) and their semantics. It explicitly names nuvio_set_setting / nuvio_unset_setting as superseded, clearly distinguishing itself from these siblings.

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?

Explicitly identifies nuvio_set_setting / nuvio_unset_setting as replaced, guiding the agent away from obsolete alternatives. It also introduces dry_run as a safe mode and nuvio_undo as the revert path. It does not fully enumerate when to use this over other profile-related update tools, but the resource scope is clear enough.

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