Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Log out a device

nuvio_revoke_session
Destructive

Revoke a single login session to log out a device. Requires a two-step confirmation token to complete; does not delete the account.

Instructions

Revoke one login session (log that device out). Cannot be undone — the device must sign in again. Never deletes the account. 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).
session_idYes
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. Changed2 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"
+}
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds meaningful behavioral detail beyond annotations: the operation cannot be undone, requires a two-phase confirmation token flow, supports dry_run, and never deletes the account. No contradiction exists.

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 concise and front-loaded with the core purpose. 'Cannot be undone' appears twice, which is mildly redundant, but the overall structure is efficient and the two-phase flow is clearly described.

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 operation with no output schema, the description covers the essential workflow, irreversibility, dry_run support, and account-safety guarantee. It does not spell out the exact return value of the first call or explicitly require session_id on the second call, but the guidance 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?

Schema coverage is 67%, so the description does not carry the full parameter burden. It adds value beyond the schema by explaining that the confirmation token is short-lived and that the operation requires calling twice. However, it does not clarify how to obtain or format session_id beyond the schema's format/pattern.

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 verb ('Revoke') and resource ('one login session'), and clarifies the purpose in plain language ('log that device out'). It also distinguishes itself from account deletion with 'Never deletes the account', which separates it from delete-style sibling tools.

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: this is for revoking a single session, is irreversible, and does not delete the account. It does not explicitly name an alternative such as nuvio_list_sessions for finding sessions, but the operational guidance about the two-phase token flow is strong.

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