dolphin-anty-mcp

Delete a proxy

delete_proxy

DestructiveIdempotent

Removes a saved proxy from the system. Profiles that referenced it are left without a proxy.

Instructions

Remove a saved proxy. Profiles referencing it are left without one.

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": {
      "id": "<id>"
    },
    "name": "delete_proxy"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already flag destructive behavior and idempotency, but the description adds crucial context beyond that: profiles referencing the proxy are left without one. This discloses a concrete side effect that an agent must know, enhancing transparency beyond the structured hints.

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?

The description is two short sentences that immediately state the purpose and the key side effect. Every word earns its place; there is no fluff or redundancy, and the action is front-loaded.

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 simple single-parameter delete tool with strong annotations (destructive, idempotent), the description covers the essential purpose and an important consequence on profiles. It doesn't mention error behaviors or return values, but these are not required for such a straightforward operation, making it adequately complete.

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?

The schema has one required parameter (id) with 0% description coverage, and the tool description does not explain the parameter's meaning or format. While the parameter is implicitly the proxy identifier from the tool name, the description fails to compensate for the lack of schema documentation, leaving the agent to infer semantics.

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 clearly states the action ('Remove a saved proxy') with a specific verb and resource, distinguishing it from sibling tools like create_proxy or update_proxy. It adds a valuable behavioral note that profiles referencing the proxy are left without one, clarifying the scope and impact beyond a simple deletion.

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 provides clear context for when to use the tool by indicating the consequence for profiles that reference the proxy. It does not explicitly mention alternatives or exclusions, but the context is sufficient for an agent to decide to use it when a proxy should be permanently removed.

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

Deploy Server