Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Export account backup

nuvio_export_backup
Read-onlyIdempotent

Export Nuvio account data as a JSON backup of profiles, addons, library, settings, and more. Credentials are excluded server-side; narrow the backup by scope, profiles, or platforms.

Instructions

Export account data as a JSON backup (profiles, addons, plugins, library, progress, history, settings, collections). Credentials and tokens are excluded server-side. With no scope this is a full backup; pass scope/profile_ids/platforms to narrow it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoSections to include (e.g. settings, addons)
platformsNoOnly these setting platforms
profile_idsNoOnly these profiles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.1
    • addedInput schema / properties / platforms
      Added value: +{
+  "description": "Only these setting platforms",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / profile_ids
      Added value: +{
+  "description": "Only these profiles",
+  "items": {
+    "maximum": 6,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "Sections to include (e.g. settings, addons)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description adds valuable behavioral context: output is JSON, credentials and tokens are excluded server-side, and scope determines full vs partial backup. This materially helps an agent understand side effects and data handling.

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 carry distinct information: what the tool returns, what it excludes, and how to control scope. It is front-loaded and contains no filler.

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

Completeness5/5

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

With no output schema, the description still conveys the output format, the data categories included, the security guarantee around credentials, and the parameter-driven scope behavior. This is sufficient for an agent to select and invoke the tool 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?

The input schema already documents all three parameters with 100% coverage, so the baseline applies. The description adds that passing them narrows the backup and that default is full backup, but it does not add meaning beyond the schema's per-parameter descriptions.

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 action ('Export'), a resource ('account data'), and the return format ('JSON backup'), then enumerates the data sections included. This clearly differentiates it from sibling tools like nuvio_restore_backup and the individual list/get tools.

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 explicit usage guidance: with no scope it is a full backup, and you can narrow it via scope/profile_ids/platforms. It does not explicitly name alternatives or say when not to use this tool, but the context is clear enough.

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