Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_script_library

Loads common JavaScript libraries into a browser environment, including jQuery, Lodash, Moment, Axios, and Chart.js; supports listing and checking library availability.

Instructions

Load common script libraries (jQuery, Lodash, etc.)

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": {
      "envId": "<envId>",
      "action": "<action>"
    },
    "name": "chrome_script_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoCustom library URL
envIdYesEnvironment ID for the browser environment to operate.
actionYesAction type: load, list, check
libraryNoLibrary name (jquery, lodash, moment, axios, chart.js)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no statement about whether the library is injected into the page, whether it persists across navigations, whether it requires an active session, or what is returned. Naming jQuery/Lodash hints at the domain but not at any behavioral trait.

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?

A single front-loaded clause with no wasted words, but the brevity comes at the cost of under-specification rather than efficiency. For a tool with three actions and four parameters, one clause is too thin a framing.

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, no output schema, and a multi-action enum, the description should explain the action modes and injection behavior. It covers only the 'load' mode and leaves 'list', 'check', custom URLs, and return values entirely to the schema.

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 coverage is 100%, so all four parameters are already documented in the schema, including the action enum and the library name list. The description's mention of jQuery/Lodash loosely echoes the 'library' parameter but adds no new meaning for envId, action, or url; baseline 3 applies.

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?

The description states a concrete verb and resource ("Load common script libraries") with recognizable examples, so the 'load' path is understandable. However, the tool's action enum includes 'list' and 'check', which the description never acknowledges, so an agent reading only the description would mischaracterize the tool's scope.

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 guidance on when to choose this over chrome_inject_script or chrome_send_command_to_inject_script, and no indication of when 'list' or 'check' should be used instead of 'load'. Prerequisites (e.g., whether a page must be loaded first) are absent.

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