Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

amazon-auto-add-cart

Searches Amazon using provided keywords, browses matching products, and adds a specified number of items to the cart in a selected browser environment.

Instructions

Visit Amazon, search for products, browse items, and add products from the list to the cart. Important: provide search keywords.

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": {
      "keyword": "<keyword>"
    },
    "name": "amazon-auto-add-cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of products to browse and add to cart. Minimum 1, maximum 10.
env_idsNoOne 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.
keywordYesProduct name or keywords for searching on Amazon.
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 largely drops it. It does not mention whether an authenticated Amazon session is required, whether the cart is the only side effect, whether items can be removed afterwards, or what happens across multiple env_ids; only the keyword prerequisite is stated.

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, front-loaded with the action sequence, with no filler or repetition of the schema. The 'Important:' clause is mildly redundant given keyword is a required field but is not wasteful enough to penalize further.

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?

This is a real-world automation task with side effects, five parameters, no annotations, and no output schema, yet the description never says what the tool returns or how success is reported. For a multi-step browser automation that mutates a shopping cart, the definition is underspecified relative to its complexity.

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%, so all five parameters (count bounds, env_ids, keyword, run_timeout, is_cancel_close) are already documented in the schema. The description only echoes the required keyword, adding no format, range, or interaction details beyond the structured fields; the baseline 3 applies.

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 names a specific verb chain and resource: search Amazon, browse items, and add products to the cart. That is far more concrete than a name-restatement, though it does not distinguish this tool from any sibling or state what differentiates it from generic browser-automation tools.

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 or when-not-to-use guidance and no alternative is named. The only directive is 'Important: provide search keywords,' which is a parameter prerequisite rather than usage context, leaving the agent to infer when this automation is appropriate versus manual browser steps.

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