Skip to main content
Glama
wiktorekdev

nuvio-mcp

by wiktorekdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a provider credential

nuvio_delete_provider_credential
Destructive

Remove a stored provider credential from a profile. Preview with dry run, then confirm to delete; previous state is snapshotted for undo.

Instructions

Remove a stored provider credential from a profile. Supports dry_run and snapshots the previous state before the write; revert with nuvio_undo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoRequired to actually apply a destructive change. Without it a preview is returned.
dry_runNoReturn the diff without writing anything (no snapshot, no audit entry).
providerYes
profile_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.1
    • changedInput schema / properties / confirm / description
      Previous value: -"Required for reversible destructive changes. Without it a preview is returned."New value: +"Required to actually apply a destructive change. Without it a preview is returned."
    • 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.0
Behavior4/5

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

Annotations already mark the tool destructive and non-read-only. The description adds valuable behavior beyond annotations: it snapshots previous state before the write and can be reverted with nuvio_undo. It does not contradict the 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?

One sentence carries purpose, dry_run behavior, snapshot behavior, and revert path with no filler or redundancy. It is front-loaded with the action.

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 key safety behavior (dry_run, snapshot, undo) but leaves provider and profile_id semantics unexplained, and with no output schema and a destructive operation, an agent still has to infer important call details. It is adequate but has clear gaps.

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 coverage is only 50%; provider and profile_id have no semantic descriptions in the schema, and the description does not clarify what values they take or their role beyond 'from a profile.' Mentioning dry_run repeats schema content rather than adding parameter meaning, so the description does not compensate for the coverage gap.

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: 'Remove a stored provider credential from a profile.' This clearly differentiates from sibling credential tools like set/test/list and matches the delete semantics implied by the name and title.

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 actionable context: dry_run is supported, a snapshot is taken before the write, and nuvio_undo can revert. It does not explicitly name alternatives or exclusion conditions, but the delete-vs-set/test/list distinction is clear enough from the tool name and context.

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