nuvio_reorder_pluginsSet the order of installed plugins by listing each plugin URL exactly once in your preferred sequence. The previous state is snapshotted, allowing you to revert with an undo operation.
Set plugin order. Provide every installed plugin URL exactly once, in the desired order. The previous state is snapshotted before the write; revert with nuvio_undo.
| Name | Required | Description | Default |
|---|---|---|---|
| profile_id | No | ||
| ordered_urls | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that the previous state is snapshotted before the write and that the operation can be undone with nuvio_undo. This adds useful behavioral context beyond the annotations, which only indicate readOnlyHint=false, idempotentHint=false, and 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three short sentences with no filler. It front-loads the core purpose, then states the critical input constraint and the undo behavior. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the main operation and undo path, but it omits the meaning of profile_id and does not mention that the plugin list may be scoped to a specific profile. Since there is no output schema and parameter descriptions are absent, this leaves a meaningful gap for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description explains ordered_urls well: it must contain every installed plugin URL exactly once, in the desired order. However, profile_id is not mentioned at all, and schema description coverage is 0%, so the description only partially compensates for the missing parameter documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the exact action ('Set plugin order') and resource ('plugins'), and immediately clarifies the key requirement: provide every installed plugin URL exactly once. This distinguishes it from sibling reorder tools like nuvio_reorder_addons and nuvio_reorder_collections.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear operational context: the caller must supply the complete set of plugin URLs exactly once, and can undo via nuvio_undo. It does not explicitly mention alternatives or when not to use the tool, but the usage condition is concrete enough to guide selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.