Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

deleteProxy

Deletes a proxy by ID from the DICloak Local API, removing it from managed browser profiles and automation setups.

Instructions

Delete proxy

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": "deleteProxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not state whether deletion is permanent, whether it revokes proxy assignments from environments, what permissions are required, or what happens if the id is invalid or in use. For a destructive mutation tool this is a critical gap.

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

Conciseness2/5

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

Two words are technically concise, but this is under-specification rather than economical writing. There is no sentence structure, no front-loaded scope statement, and nothing that earns its place beyond echoing the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive one-parameter tool with no annotations, no output schema, and an undocumented parameter, the description should explain effect, irreversibility, and identifier semantics. None of that is present, so an agent cannot call this tool safely or correctly from the definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter 'id', and the description does nothing to compensate. It never clarifies whether 'id' is the proxy's numeric identifier, name, or UUID, nor what format is expected.

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

Purpose2/5

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

The description 'Delete proxy' merely restates the tool name as a verb-plus-resource pair and adds no scope, target, or effect information. It does, however, at least distinguish the operation class (deletion) from siblings like checkProxy, createProxy, and updateProxy, which keeps it above a pure tautology.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of prerequisites (such as whether the proxy must be disabled or unassigned first), and no reference to alternatives like updateProxy or checkProxy. The agent must guess the conditions under which this tool is appropriate.

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