DoubleData MCP

Delete proxy credential

delete_credential

DestructiveIdempotent

Permanently delete a proxy credential by confirming the username; any service using it stops working immediately.

Instructions

Permanently delete a proxy credential. Anything using it stops working immediately. Set confirm_username to the same username to proceed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>",
      "confirm_username": "<confirm_username>"
    },
    "name": "delete_credential"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes
`confirm_username`	Yes	Repeat the username to confirm deletion.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description adds real value on top by stating the effect is permanent and takes effect immediately for anything consuming the credential. It stops short of saying whether a mismatched confirm_username produces an error or whether the call fails for unknown usernames.

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: the action, the consequence, and the procedural requirement. The most important information (permanence) is front-loaded and there is no filler.

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 two-parameter destructive tool with no output schema and strong annotations, the description covers action, irreversibility, side effects, and the confirmation mechanism. Only error behavior on mismatch or unknown username is left unstated.

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?

With 50% schema coverage, the schema documents confirm_username but not username or its pattern. The description clarifies that confirm_username must equal username, which reinforces the equality constraint, but adds nothing about the username format, length limits, or what happens on mismatch.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Permanently delete a proxy credential" gives a specific verb and resource, and the immediacy clause makes the outcome unambiguous. It does not explicitly name the sibling it contrasts with (list_credentials, create_credential), but the intent is clear without opening any schema.

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

Usage Guidelines3/5

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

The permanence and "anything using it stops working immediately" warning implies this is the destructive path and should be used deliberately, and the confirm_username requirement signals a guard. However, there is no explicit when-to-use vs. alternative guidance (e.g., to rotate rather than delete, use a different tool), and no note that the credential must already exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.