Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

cookie-robot

Automate browsing specified website URLs and collect cookie information from designated DICloak environments; provide site URLs and environment IDs to run the task.

Instructions

Automatically browse specified websites and collect cookie information. Important: provide a list of site URLs.

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": {
      "env_ids": "<env_ids>",
      "urls": "<urls>"
    },
    "name": "cookie-robot"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesList of website URLs to collect cookies from. Example: ["https://example.com", "https://another.com"]
env_idsYesOne or more environment IDs where this task should run. If the user did not provide environment details (name, id, remark, serial number), prompt for them or offer to help create an environment.
run_timeoutNoOverall process timeout in seconds. The environment will be closed automatically after this period.
is_cancel_closeNoShould the environment be closed after the execution is completed? 0 means close, 1 means do not close. The default is 0. If you set it to 1, please set run_timeout to 0 to avoid automatic closing due to timeout.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 mostly does not meet it. It never says this launches a long-running job in an environment, that the environment is closed afterward, or what happens on partial failure or timeout. Only the word "Automatically" hints at asynchronous execution, and that is left for the agent to infer.

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

Conciseness4/5

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

Two short sentences with the action stated first and the required input called out second. Nothing is padded, though the "Important:" framing is a weak use of the limited space that could have carried real behavioral context instead.

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?

With no annotations and no output schema, the description is the only place an agent can learn the execution model, and it does not. It omits the asynchronous job nature, environment lifecycle behavior, timeout implications, and what "cookie information" is returned. For a 4-parameter tool that spins up environments, that is a substantial gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including per-parameter docs for urls, env_ids, run_timeout and the is_cancel_close enum, so the baseline of 3 applies. The description reinforces that urls is mandatory but adds no syntax, format or constraint detail beyond the schema examples.

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

Purpose4/5

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

The description gives a concrete verb pair and resource: "browse specified websites and collect cookie information." That is clearly distinct from the Chrome element/network siblings, which operate on a live session rather than harvesting cookies. It stops short of naming any sibling or contrasting scopes, so it lands at 4 rather than 5.

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?

"Important: provide a list of site URLs" is a parameter requirement, not usage guidance. There is no statement of when to choose this tool over the Chrome browsing/crawling siblings, nor any prerequisite or exclusion. An agent knows what the tool does but not when it should reach for it.

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