Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

getProxyInfo

Retrieve proxy details by ID to inspect configuration and status for a specific proxy in DICloak.

Instructions

Get proxy details

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/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 it says nothing beyond "details." It does not indicate whether the response includes sensitive proxy credentials, whether a specific permission or proxy state is required, or what happens when the id is unknown. The only implicit signal is that "Get" suggests a non-mutating read.

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

Conciseness3/5

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

Three words, front-loaded, with no wasted phrasing, but the brevity comes at the cost of substance rather than from disciplined editing. There is no structure to speak of because there is almost no content.

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

Completeness2/5

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

For a simple single-parameter lookup the description could be adequate in size, but with no annotations, no output schema, and zero schema coverage, the agent has no information about what "details" contains or how the `id` is formed. It falls short of what is needed to call the tool correctly the first time.

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 not compensate at all: it never states whether `id` is a proxy identifier, an environment identifier, a numeric index, or a UUID. The one parameter that determines whether the call succeeds is completely undocumented.

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

Purpose3/5

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

"Get proxy details" does state a verb and a resource, so the basic action is inferable, but "details" is undefined and the description makes no attempt to distinguish this from close siblings such as checkProxy or updateProxy. An agent cannot tell from the text whether this returns configuration, connection status, or both.

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 mention of prerequisites, and no routing to alternatives such as checkProxy for status checks. The agent is left to infer the tool's role from the name alone.

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