Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Copy setup between profiles

nuvio_copy_profile_setup

Copy TV, mobile, or desktop settings between Nuvio profiles, optionally including provider credentials. Use dry-run to preview changes and snapshots to revert.

Instructions

[DEPRECATED] Use nuvio_copy_setup instead. Copy TV/mobile/desktop settings (and optionally provider credentials) from one profile to another. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
copy_tvNo
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
copy_mobileNo
copy_desktopNo
source_profile_idYes
target_profile_idYes
copy_provider_credentialsNo
replace_provider_credentialsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Return the diff without writing anything (no snapshot, no audit entry).",
+  "type": "boolean"
+}
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate non-readonly, non-idempotent, and non-destructive. The description adds that it snapshots the previous state before writing and supports dry_run, which are valuable behavioral details beyond the annotations. It also mentions revert via nuvio_undo, providing operational context.

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 a single sentence that front-loads the deprecation notice and packs in the core function, dry_run support, and snapshot/undo behavior. It is concise and clear, though it crams a lot of information into one sentence.

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 8 parameters and no output schema, the description is minimal. It omits details about the credential flags, return values, and the exact semantics of the snapshot. However, since it directs users to the replacement, the lack of completeness is somewhat mitigated.

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 13% (only dry_run has a description). The description partially compensates by mentioning the copy_tv/mobile/desktop and provider credentials parameters, but it does not clarify the distinction between copy_provider_credentials and replace_provider_credentials, nor does it explain the profile ID semantics beyond the schema. Given the low coverage, this is insufficient.

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 the tool copies TV/mobile/desktop settings and optionally provider credentials between profiles, and it explicitly names the replacement sibling (nuvio_copy_setup), distinguishing itself from it. The deprecated flag is front-loaded and unambiguous.

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?

It explicitly instructs the agent to use nuvio_copy_setup instead, which is direct guidance on when not to use this tool. It also mentions dry_run and snapshot/undo capabilities, which indicate safe usage patterns.

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