Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

checkProxy

Verifies proxy connectivity and configuration from host, port, type, and credentials, returning status to diagnose failures before use with DICloak profiles.

Instructions

Check proxy

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "checkProxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNo
portNo
typeNoProxy type
ipTypeNo
passwdNo
remarkNo
statusNo
userNameNo
ipAddrTypeNo
proxySettingTypeNo

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?

With no annotations, the description carries the full behavioral burden, yet it discloses nothing: no indication whether this is a read-only probe or a mutating operation, whether it makes network calls that could be slow or rate-limited, what auth is needed, or what happens on failure.

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?

The text is short, but that brevity reflects under-specification rather than economy; there is no structure, no front-loaded statement of effect, and no information that earns its place.

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?

A 10-parameter tool with 5 enums, no required parameters, no annotations, and no output schema needs substantial explanation of what a "check" returns and how optional filters interact. The two-word description is completely inadequate for that complexity.

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?

Ten parameters with only 10% schema description coverage, and the description adds zero meaning. Critical ambiguities are unaddressed, e.g. whether host/port/passwd/userName are inputs to test or filters for selection, and what status means as an input versus an outcome.

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?

"Check proxy" only restates the tool name. "Check" is ambiguous — it could mean validate credentials/connectivity, retrieve status, or test reachability. Nothing distinguishes it from siblings like getProxyInfo or updateProxy.

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 alternatives such as getProxyInfo, and no prerequisites or exclusions. The agent must guess the tool's role in the proxy lifecycle.

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