Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Reorder addons

nuvio_reorder_addons

Set the display order of a profile's addons by submitting every installed addon URL in the desired sequence. Preview changes with dry run; previous state is snapshotted for revert via undo.

Instructions

Set the display order of a profile's addons. Provide every installed addon 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.2/5.0
Behavior4/5

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

The description discloses the snapshot-before-write behavior and the undo path via nuvio_undo, which is not present in the annotations. It also mentions dry_run and its effect (no snapshot/audit). These add meaningful behavioral context beyond the structured fields, though it does not detail return values or failure modes.

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 two sentences with no fluff. It front-loads the purpose, includes the critical ordered_urls constraint, and mentions dry_run and snapshot/undo—all essential. Every sentence 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?

Given that this is a write operation with no output schema, the description covers the main operational aspects: required input format, dry_run behavior, and revertibility. It does not specify the return value or explicitly state prerequisites like profile existence, but the snapshot and undo details make it adequately complete for an agent to call it correctly.

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 33% (dry_run only). The description adds value for ordered_urls by specifying the 'exactly once' requirement, which is not in the schema. However, profile_id is not explained in the description, and the schema already provides its default/range. The description partially compensates for low coverage but does not fully clarify all parameters.

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: 'Set the display order of a profile's addons.' This is unambiguous and distinguishes from sibling tools like nuvio_reorder_plugins by explicitly naming 'addons' and 'profile.' It also names the core operation (display order) clearly.

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 provides a key usage rule: 'Provide every installed addon URL exactly once, in the desired order,' which is essential for correct invocation. It implicitly scopes the tool to addons, and the sibling list makes alternatives obvious, but it does not explicitly state when not to use it (e.g., for plugins). The dry_run and snapshot guidance also help decide usage.

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