Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Reorder plugins

nuvio_reorder_plugins

Reorder installed plugins by specifying each plugin URL in the desired order. Preview changes with dry run, and undo if needed.

Instructions

Set plugin order. Provide every installed plugin URL exactly once, in the desired order. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

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

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 / ordered_urls / items / format
      Removed value: -"uri"
    • addedInput schema / properties / ordered_urls / items / minLength
      Added value: +1
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations show destructiveHint=false and readOnlyHint=false, and the description adds that 'snapshots the previous state before the write' and supports dry_run, disclosing side effects beyond the schema. It also notes that dry_run skips the snapshot/audit, which is useful behavioral context.

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?

Three sentences with high information density—states the essential constraint (all URLs exactly once), mentions dry_run and snapshot features, and points to revert tool. No filler.

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?

The description is complete for a reorder operation with dry_run and revert, but it lacks details on return values (no output schema) and doesn't elaborate on profile_id or validation errors. Given complexity and missing output schema, more context could help, but the core behavior is covered.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is low (33%), with dry_run and profile_id lacking description in the schema. The description only mentions ordered_urls implicitly ('every installed plugin URL exactly once') but doesn't explain dry_run or profile_id semantics. Since the description adds meaning only for ordered_urls, and 2 of 3 params are undocumented, it partially compensates but leaves gaps.

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 a specific verb and resource ('Set plugin order') and provides the unique constraint (every plugin URL exactly once), distinguishing this from nuvio_add_plugin and nuvio_update_plugin. The action is unambiguous.

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?

It implies when to use it—when reordering is needed—and mentions dry_run and revert capabilities, but doesn't explicitly list sibling tools or state when NOT to use. Still, the context of reordering is clear against other plugin operations.

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