Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Clear a profile PIN

nuvio_clear_profile_pin
Destructive

Remove a profile's PIN lock using a two-step process: first call to get a confirmation token, then call again with that token to finalize. Irreversible, with optional dry-run to preview changes.

Instructions

Remove the PIN lock from a profile. Not reversible. 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
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"
-]New value: +[
+  "profile_id"
+]
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond annotations (destructiveHint=true), the description discloses that the operation is irreversible, not idempotent, requires a two-phase confirmation token, and that the token is short-lived. It also mentions dry_run support. This is valuable behavioral context that the annotations alone do not provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded with the core purpose. The only minor issue is 'Not reversible. Cannot be undone.' is somewhat redundant, but the overall structure is efficient and scannable.

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 destructive, two-phase tool with no output schema, the description covers the essential call flow, irreversibility, and dry_run option. It leaves current_pin's purpose undocumented and does not describe the response format, but the token-handling instructions are sufficient for an agent to call 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 description substantially clarifies confirmation_token by explaining the two-phase prepare/execute flow, but it does not explain current_pin or profile_id beyond what the schema already shows. With 50% schema description coverage, it adds some value but does not fully compensate for the missing 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 names the exact action and resource: 'Remove the PIN lock from a profile.' This clearly distinguishes it from the sibling nuvio_set_profile_pin, and the added detail about irreversibility and the two-phase flow makes the tool's role unmistakable.

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 gives clear context for when to call it and how: remove a PIN, call once for a token, then call again with that token. It does not explicitly compare against nuvio_set_profile_pin or state exclusions, but the purpose and call sequence are clear enough for an agent 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