Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update tracker settings

nuvio_set_tracker_settings

Set statuses, row order, and progress syncing for linked trackers. Supports dry-run and snapshot-based undo to revert changes safely.

Instructions

Set which statuses sync, row order and progress syncing for a linked tracker. 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).
trackerYesTracker: mal | anilist | kitsu
row_orderNo
profile_idNo
send_progressNo
enabled_statusesNo

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.1/5.0
Behavior5/5

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

Annotations only indicate the tool is not read-only; the description goes further by disclosing dry_run behavior, snapshotting of the previous state before the write, and a revert path via nuvio_undo. This gives an agent a clear preview-and-recovery model beyond the structured annotations.

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?

Two tight sentences with no filler: the core action and scoped fields appear first, followed by the dry_run and revert behavior. Every sentence earns its place.

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 covers the core operation, dry-run behavior, and revert path, but it is thin on parameter details such as profile_id and valid array values, and there is no output schema to clarify the response. With six parameters, this leaves some call details to inference.

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%, and the description maps enabled_statuses, row_order, and send_progress to their conceptual roles, which partially compensates. However, profile_id is left unexplained, and the expected string values for row_order and enabled_statuses arrays are not provided.

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?

States a specific verb and resource ('Set ... tracker settings') and names the concrete fields changed: statuses sync, row order, and progress syncing. The 'linked tracker' qualifier clearly separates it from general settings tools like nuvio_update_settings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context that this targets a linked tracker's sync settings and mentions dry_run for previewing changes, but it does not explicitly name alternatives or exclusion criteria, such as when to prefer nuvio_update_settings or what to do if no tracker is linked.

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