Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Enable or disable an addon

nuvio_toggle_addon

Turn an addon on or off for a profile. Supports dry-run and snapshots previous state for undo; use nuvio_update_addon instead.

Instructions

[DEPRECATED] Use nuvio_update_addon instead. Turn one addon on or off for a profile. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
enabledYes
profile_idNo

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"
+}
    • removedInput schema / properties / url / format
      Removed value: -"uri"
    • addedInput schema / properties / url / minLength
      Added value: +1
  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 the tool is not read-only and not destructive. The description adds valuable behavioral detail: it snapshots the previous state before the write, supports dry_run, and can be reverted with nuvio_undo. This goes beyond the structured annotations and clarifies the write/revert workflow.

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 pack the deprecation warning, replacement tool, purpose, and key behavioral safeguards without any filler. The most important routing information (deprecated, use alternative) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite a clear purpose and behavior disclosure, the description is incomplete for a tool with five parameters and no output schema. It does not explain how to select or provide the addon (id vs url), what profile_id means beyond a default, or what success/return values look like. The deprecation lowers stakes, but if invoked, an agent still lacks key calling details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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, but it fails to clarify how id, url, and profile_id are used to identify the addon or how enabled maps to the toggle. It only adds 'turn on/off' and 'supports dry_run,' which largely restates the schema. Critical parameter relationships (e.g., id vs url) are left unexplained.

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 action ('Turn one addon on or off for a profile'), names the resource (addon), and immediately distinguishes it from the preferred alternative by marking it deprecated and pointing to nuvio_update_addon. An agent can tell exactly what this tool does and how it relates to siblings.

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 'Use nuvio_update_addon instead,' providing a direct when-not-to-use instruction and naming the alternative. It also mentions the supporting behaviors (dry_run, snapshot, revert) that would inform when the tool might still be useful.

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