Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create a Nuvio profile

nuvio_create_profile

Create a new Nuvio profile while preserving all existing profiles. Supports up to 6 profiles, dry-run previews, and snapshot/undo for safe changes.

Instructions

Add a new profile, preserving every existing one. Max 6 profiles; slot 1 is primary. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
avatar_idNoAvatar catalog id (see nuvio_list_avatars)
avatar_urlNo
profile_idNoSlot 1..6; auto-picked if omitted
avatar_color_hexNo
uses_primary_addonsNoShare addons with profile 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / profile_id
      Added value: +{
+  "description": "Slot 1..6; auto-picked if omitted",
+  "maximum": 6,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / profile_index
      Removed value: -{
-  "description": "Slot 1..6; auto-picked if omitted",
-  "maximum": 6,
-  "minimum": 1,
-  "type": "integer"
-}
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

The description goes beyond the annotations by disclosing that the tool preserves existing profiles, enforces a max of 6, supports dry_run, snapshots the previous state before writing, and can be reverted with nuvio_undo. This is rich behavioral context that an agent would not otherwise derive from readOnlyHint=false or destructiveHint=false.

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 carry the core action, constraints, dry-run behavior, snapshot guarantee, and rollback path with no filler. The most important information is front-loaded, and every clause 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?

The description covers the essential operational context: creation, non-destructive behavior, limits, primary-slot semantics, dry_run, and undo path. It does not specify error handling when the 6-profile cap is reached or describe return behavior, but given the absence of an output schema and the presence of rich sibling context, it is reasonably 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 57%, so several parameters (name, avatar_url, avatar_color_hex) lack schema descriptions, and the tool description does not explain them. It does add useful meaning for dry_run and the primary slot rule, but it only partially compensates for the coverage gap.

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 states a specific verb and resource ('Add a new profile') and adds a key constraint ('preserving every existing one'), which clearly distinguishes it from update/delete/list siblings. The max-6 and primary-slot details further pin down the operation's scope.

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?

The description clearly indicates creation as opposed to the sibling update/delete/list tools through 'Add a new profile'. It provides relevant context such as the 6-profile cap and primary slot rule, but does not explicitly name alternatives or when-not-to-use conditions, so it falls short of a 5.

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