Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set a profile PIN

nuvio_set_profile_pin
Destructive

Set or change the PIN lock on a profile. Use a two-phase token to confirm irreversible changes, with optional dry-run preview.

Instructions

Set or change the PIN lock on a profile. Not reversible (the PIN hash is never returned). Cannot be undone: call it once to get a short-lived confirmation token, then call again with that token. Supports dry_run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pinYes
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
profile_idYes
current_pinNo
confirmation_tokenNoToken from a previous call of this tool. Irreversible operations require a two-phase prepare/execute: call once to receive the token, then call again with it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.1
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Required for reversible destructive changes. Without it a preview is returned.",
-  "type": "boolean"
-}
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Return the diff without writing anything (no snapshot, no audit entry).",
+  "type": "boolean"
+}
    • addedInput schema / properties / profile_id
      Added value: +{
+  "maximum": 6,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / profile_index
      Removed value: -{
-  "maximum": 6,
-  "minimum": 1,
-  "type": "integer"
-}
    • changedInput schema / required
      Previous value: -[
-  "profile_index",
-  "pin"
-]New value: +[
+  "profile_id",
+  "pin"
+]
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark destructive, non-readOnly, non-idempotent. The description adds crucial behavioral context: irreversibility, that the PIN hash is never returned, and the two-phase confirmation flow with dry_run. No contradiction.

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 dense sentences with no filler; purpose, irreversibility, and dry-run support are front-loaded and each sentence adds value.

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?

The description covers the non-reversible two-phase flow and dry_run, which is the essential complexity. It does not explicitly state the return value beyond the indirect mention of a token, but this is inferable and not required for correct invocation.

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 40%, so the description must compensate. It explains confirmation_token's role and mentions dry_run, but does not describe profile_id, pin, or current_pin beyond what their names imply. Adequate but incomplete compensation.

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 or change the PIN lock on a profile'), clearly distinguishing from sibling clear_profile_pin. The two-phase irreversibility note reinforces what action the tool performs.

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?

Explicitly describes the required call sequence (first call to get token, second with token) and supports dry_run. Does not name alternatives or exclusions, but the intended use is clear from 'Set or change' and the two-phase instructions.

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