Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Enable or disable a plugin

nuvio_toggle_plugin

Enable or disable a plugin for a profile, with dry-run support and automatic snapshot for undo/rollback.

Instructions

[DEPRECATED] Use nuvio_update_plugin instead. Turn one plugin 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
urlYes
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

A3.8/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations: it states that the tool 'supports dry_run' (a non-destructive mode) and 'snapshots the previous state before the write; revert with nuvio_undo.' This explains reversibility and safety, which the annotations (readOnlyHint=false, destructiveHint=false) do not fully convey. It does not contradict annotations.

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?

The description is extremely concise—two sentences—and front-loads the deprecation warning, which is the most critical information. It then packs the essential behavior (toggle, dry_run, snapshot, revert) into a short, scannable format. Every word earns its place.

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?

For a tool with 4 parameters, 2 required, no output schema, and only 25% parameter documentation, the description does not provide enough to call it correctly. It fails to explain url and profile_id, and the deprecation status does not absolve the need for parameter clarity if the tool is still invocable. The snapshot/revert workflow is mentioned but not detailed.

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?

Only one of four parameters (dry_run) has a description in the schema (25% coverage). The tool description does not explain url, enabled, or profile_id beyond implying that 'enabled' toggles the plugin and the action is per-profile. This is insufficient for an agent to understand what url points to or how profile_id is used. The description fails to compensate for the low schema coverage.

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 clearly states the tool's function: 'Turn one plugin on or off for a profile.' It also explicitly names the preferred alternative (nuvio_update_plugin), which distinguishes it from siblings. The deprecation notice adds context without obscuring the core action.

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 opens with '[DEPRECATED] Use nuvio_update_plugin instead,' giving an explicit directive to avoid this tool in favor of a sibling. It also mentions the dry_run option and the snapshot/revert workflow, which helps an agent decide when to use it (e.g., for a quick toggle with safety) and when not to.

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