Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set a provider credential

nuvio_set_provider_credential

Store an API key or client ID for supported providers like TorBox, Real-Debrid, TMDB, and others, with optional dry-run and undo support via snapshot before write.

Instructions

Store an API key for a provider: debrid:torbox, debrid:premiumize, debrid:realdebrid, tmdb, mdblist, introdb (api key) or animeskip (client id). Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesAPI key / client id value
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
providerYesOne of the supported provider ids
profile_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Return the diff without writing anything (no snapshot, no audit entry).",
+  "type": "boolean"
+}
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish this as a write operation, and the description adds valuable behavior beyond that: it snapshots the previous state before writing and supports undo via nuvio_undo. This is meaningful context not available from annotations alone, though it does not detail side effects of overwriting an existing key.

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?

A single, compact sentence that front-loads the action, packs the provider list efficiently, and tacks on dry_run/snapshot/undo behavior without filler. Every clause 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?

For a small mutation tool with no output schema, the description covers what the tool does, which provider values are accepted, and what safety/undo mechanisms exist. The only notable gap is that profile_id semantics are left to inference, but the overall definition is sufficient for correct invocation.

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?

The schema only says provider is "One of the supported provider ids," while the description lists the actual accepted values and distinguishes API key vs client id for animeskip. It also reinforces dry_run semantics. The profile_id parameter is not explained in the description, but its schema constraints (default 1, range 1–6) provide partial context.

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 and resource: "Store an API key for a provider," then enumerates the exact supported provider values. It is clearly distinct from the sibling list/test/delete credential tools because the verb and intent are explicit.

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 makes the use case clear: store/set a provider API key, with dry_run as a safe preview option. It does not explicitly contrast itself with nuvio_test_provider_credential or nuvio_delete_provider_credential, but the verb and provider list give enough context to select it correctly.

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