Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

listProxies

Retrieve and filter proxies by ID, host, type, environment, or remark, with pagination and optional details. Use it to inspect or page through available proxies before assigning them to profiles.

Instructions

List proxies

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

Input Schema

NameRequiredDescriptionDefault
idNo
allNo
envNo
hostNo
typeNo
detailNo
remarkNo
page_noNo
page_sizeNo
serial_numNo

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 burden and provides none of it: no mention of pagination behavior (page_no/page_size exist), no default result set, no return shape, no permission or rate-limit context. For a read tool with 10 optional parameters, this is a complete 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 with nothing to trim, but this is under-specification rather than economy. There is no front-loaded information because there is no information.

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?

Given 10 undocumented parameters, zero annotation coverage, and no output schema, the definition should explain filtering, paging, and return content. None of that is present, so the definition is inadequate for the tool's 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?

Schema description coverage is 0% across 10 parameters, and the description adds no meaning for any of them. An agent cannot learn from the text whether id/host/type/remark are exact-match filters, what all=true does, what detail toggles, or how serial_num differs from id.

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?

"List proxies" restates the tool name (listProxies) and gives no more specificity than the identifier already does. It does convey the verb+resource, but nothing distinguishes it from sibling listing tools such as listEnvs or listEnvGroups, and no scope or filtering intent is stated.

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 exclusions, and no mention of alternatives like checkProxy or createProxy. The agent is left to infer entirely from the name whether this is a filtered lookup, a paged enumeration, or both.

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