Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

createProxy

Creates HTTP, HTTPS, IPFLY, or SOCKS5 proxy entries in DICloak with host, port, and optional credentials so AI assistants can manage browser profile network access.

Instructions

Create 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": {
      "type": "<type>",
      "host": "<host>",
      "port": "<port>"
    },
    "name": "createProxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
portYes
typeYes
passwdNo
remarkNo
user_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full disclosure burden and delivers none of it: no statement about permissions or authentication needed, whether creation fails on duplicates, whether credentials are stored, or whether the operation is reversible. For a mutation tool that accepts user_name/passwd secrets, this silence is a serious 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 is not conciseness but under-specification; there is no front-loaded explanation of purpose, inputs, or effects. Nothing in the text could be trimmed because nothing informative is present.

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?

With six parameters, three required, an enum type, credential fields, and no annotations or output schema, the definition is far too thin for an agent to call it correctly. It supplies none of the context the structured fields leave out.

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% across 6 parameters, and the description explains none of them. The meaning of user_name/passwd pairing, what remark is for, how host and port combine for each of the HTTP/HTTPS/IPFLY/SOCKS5 types, and which fields are conditionally required are all left entirely undocumented.

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?

"Create proxy" merely restates the tool name with a verb and a resource noun; it adds no scope, target system, or distinguishing detail. Siblings such as updateProxy, deleteProxy, checkProxy and getProxyInfo make it obvious which CRUD verb is involved, but the description does nothing to say what kind of proxy entity is created or how it differs from those siblings.

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

Usage Guidelines2/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 prerequisites, and no mention of alternatives or follow-up steps (e.g. verify with checkProxy after creation). The name implies a write operation, but nothing states when a proxy should be created or what conditions would make updateProxy the better choice.

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