Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Link a tracker

nuvio_link_tracker

Store OAuth access tokens for linking a tracker (MAL, AniList, Kitsu) to a profile when tokens are obtained out-of-band. Supports dry-run and snapshots the previous state for undo.

Instructions

Store tracker OAuth tokens for a profile. Use this only when tokens were obtained out-of-band; prefer the app sign-in flow. 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
usernameNo
profile_idNo
access_tokenYes
refresh_tokenNo
tracker_user_idNo
expires_in_secondsNo

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.2/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds concrete behavior beyond the annotations: dry_run is supported, a snapshot of the previous state is taken before the write, and nuvio_undo can revert it.

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 short sentences, with the core purpose first and no filler. Each sentence adds either scope, usage guidance, or side-effect information.

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 key usage rule and write behavior are covered, but with 8 parameters, 25% schema coverage, and no output schema, several optional fields remain unexplained. Still, an agent can call the primary path safely using tracker and access_token.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, so the description needed to compensate. It clarifies tokens relate to OAuth and that a profile is targeted, but it does not explain username, tracker_user_id, expires_in_seconds, refresh_token, or how dry_run interacts with the snapshot beyond what the schema already says.

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 opens with a specific verb and resource: 'Store tracker OAuth tokens for a profile.' It also draws the boundary with the out-of-band token flow, so an agent can distinguish this linking operation from nuvio_unlink_tracker and nuvio_list_trackers.

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

Usage Guidelines5/5

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

'Use this only when tokens were obtained out-of-band; prefer the app sign-in flow' explicitly states when the tool is appropriate and gives the preferred alternative. This is clear routing with no ambiguity.

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