Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set a nested setting

nuvio_set_setting

Set a nested setting value using a dot path, with dry-run support and automatic snapshot for undo via nuvio_undo. Deprecated; use nuvio_update_settings.

Instructions

[DEPRECATED] Use nuvio_update_settings instead. Set one nested value by dot path. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
valueYes
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
platformNotv
profile_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
+}
    • removedInput schema / properties / path / description
      Removed value: -"Dot path into settings_json"
    • removedInput schema / properties / platform / description
      Removed value: -"Platform namespace: tv | mobile | desktop | web"
    • removedInput schema / properties / value / description
      Removed value: -"Any JSON value"
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds valuable behavioral context: it snapshots the previous state before the write, supports dry_run, and can be reverted with nuvio_undo. This goes beyond the annotations and helps the agent understand side effects and safety.

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?

The description is compact and front-loaded with the deprecation warning, which is the most important routing information. It packs snapshot, dry_run, and revert behavior into one sentence without waste, though it could be slightly clearer about parameter semantics.

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?

For a deprecated tool with no output schema, the description covers the key behavioral aspects (snapshot, dry_run, revert) and routing. However, it doesn't explain what the return value looks like, how the dot path is validated, or what happens on failure. Given the tool's complexity and the low schema coverage, a bit more detail would be helpful.

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 only 20%, so the description must compensate. It explains 'path' as a dot path and mentions 'dry_run' behavior, but it doesn't clarify 'value', 'platform', or 'profile_id' beyond the schema defaults. The description adds some meaning but leaves several parameters under-explained.

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 specific verb ('Set') and resource ('one nested value by dot path'), and clearly marks the tool as deprecated in favor of nuvio_update_settings. It distinguishes itself from the sibling by noting it sets a single nested value by dot path, though it doesn't fully explain what nuvio_update_settings does differently.

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

Usage Guidelines5/5

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

The description explicitly says '[DEPRECATED] Use nuvio_update_settings instead,' which is a direct when-to-use/alternative instruction. It also mentions dry_run support and the revert path via nuvio_undo, giving clear context for when this tool might still be used.

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