Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

updateProxy

Modify an existing proxy's connection and authentication settings by ID, including type, host, port, credentials, IP lookup type, status, and remark, to correct routing for DICloak browser profiles.

Instructions

Update 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>",
      "type": "<type>",
      "host": "<host>",
      "port": "<port>",
      "user_name": "<user_name>",
      "passwd": "<passwd>",
      "ip_type": "<ip_type>"
    },
    "name": "updateProxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
hostYes
portYes
typeYes
out_ipNo
passwdYes
remarkNo
statusNo
ip_typeYes
user_nameYes

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 supplied, so the description carries the full behavioral burden and discloses nothing. It does not say whether this is a full replace or partial patch (7 of 10 params are required, implying replace), what happens to omitted fields, whether credentials are required, or what side effects occur on live traffic.

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 with zero filler, but this is under-specification rather than conciseness. Nothing is front-loaded because nothing is present beyond a restated 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 10-parameter mutation tool with no annotations, no output schema, and no schema descriptions, the description is completely inadequate. An agent cannot safely invoke this without guessing at required-vs-optional semantics and enum values.

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 10 parameters, including three enums (type, status, ip_type) whose meanings are unstated. The description adds no meaning for any parameter, leaving enum semantics, formats, and the required-field requirement entirely unexplained.

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?

"Update proxy" only restates the tool name with no resource detail, no statement of what fields are mutable, and no distinction from the many sibling mutators (createProxy, deleteProxy, updateEnv). It is essentially a tautology rather than a purpose statement.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives. An agent has no basis for choosing this over createProxy or checkProxy, and nothing indicates whether the target proxy must already exist.

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