Skip to main content
Glama
Sign In
wopee-mcp

wopee-mcp

Official
by Wopee-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Dispatch analysis crawl

wopee_dispatch_analysis

Create an analysis suite and dispatch an AI browser agent to crawl a web app, discover pages, and map its structure in one step.

Instructions

Create a new analysis suite AND dispatch an AI crawling agent in one step. The agent opens a real browser, navigates from the starting URL, discovers pages, and maps the application structure. Use this when you want to auto-analyze a web app — it combines suite creation and crawling. Use wopee_create_blank_suite instead if you want to manually populate the suite. Optionally accepts starting URL, login credentials, cookie preferences (ACCEPT_ALL, DECLINE_ALL, IGNORE), custom variables, and free-text instructions to guide the crawl. Not idempotent: each call creates a new suite and starts a new crawl. Side effects: creates a suite and execution records on the platform. Rate limit: 10 seconds between dispatches per project; concurrent calls auto-retry with exponential backoff. Returns the created suite object on success.

Input Schema

NameRequiredDescriptionDefault
rerunNoIf provided, reruns an existing analysis suite instead of creating a new one. Requires suiteUuid, analysisIdentifier, and mode.
additionalVariablesNoAdditional environment variables for the analysis. Each variable needs a key (uppercase, e.g. BASE_URL) and a non-empty value.
additionalInstructionsNoAdditional instructions for the agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.32.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / additionalVariables / anyOf
      Previous value: -[
-  {
-    "description": "Additional environment variables for the analysis. Each variable needs a key (uppercase, e.g. BASE_URL) and a non-empty value.",
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "key": {
-          "description": "Variable name. Must be uppercase with underscores only (e.g. MY_VAR, BASE_URL).",
-          "pattern": "^[A-Z_][A-Z0-9_]*$",
-          "type": "string"
-        },
-        "value": {
-          "description": "Variable value. Must be a non-empty string.",
-          "minLength": 1,
-          "type": "string"
-        }
-      },
-      "required": [
-        "key",
-        "value"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "properties": {
+        "key": {
+          "description": "Variable name. Must be uppercase with underscores only (e.g. MY_VAR, BASE_URL).",
+          "pattern": "^[A-Z_][A-Z0-9_]*$",
+          "type": "string"
+        },
+        "value": {
+          "description": "Variable value. Must be a non-empty string.",
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "key",
+        "value"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / rerun / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "analysisIdentifier": {
-        "description": "Analysis identifier of the existing suite to rerun.",
-        "minLength": 1,
-        "type": "string"
-      },
-      "mode": {
-        "description": "Rerun mode: FULL reruns the entire analysis (crawling + analysis), CRAWLING reruns only the crawling phase.",
-        "enum": [
-          "FULL",
-          "CRAWLING"
-        ],
-        "type": "string"
-      },
-      "suiteUuid": {
-        "description": "UUID of the existing suite to rerun.",
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "suiteUuid",
-      "analysisIdentifier",
-      "mode"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "analysisIdentifier": {
+        "description": "Analysis identifier of the existing suite to rerun.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "mode": {
+        "description": "Rerun mode: FULL reruns the entire analysis (crawling + analysis), CRAWLING reruns only the crawling phase.",
+        "enum": [
+          "FULL",
+          "CRAWLING"
+        ],
+        "type": "string"
+      },
+      "suiteUuid": {
+        "description": "UUID of the existing suite to rerun.",
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "suiteUuid",
+      "analysisIdentifier",
+      "mode"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description does meaningful work by disclosing side effects (suite and execution records), rate limiting, retry behavior, and the return value. However, it misstates behavior by saying 'each call creates a new suite' and 'not idempotent,' while the schema allows rerunning an existing suite via the rerun parameter.

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?

The description is front-loaded and mostly efficient, covering purpose, alternative, side effects, rate limits, and return value in a compact block. A few details are inaccurate rather than verbose, so structure is strong but content quality is reduced.

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

Completeness3/5

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

For a complex dispatch-and-create tool with no annotations and no output schema, the description covers many operational details. It is still incomplete and somewhat misleading because it does not explain the rerun mode and references crawl parameters that the schema does not expose.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline would be 3. But the description actively mentions parameters that are not present in the schema (starting URL, login credentials, cookie preferences) and omits the important rerun parameter, creating confusion about what inputs are actually accepted.

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 clearly states a specific verb and resource: creating an analysis suite and dispatching an AI crawling agent. It distinguishes itself from wopee_create_blank_suite and explains the crawling behavior. However, it says each call creates a new suite even though the schema exposes a rerun path for existing suites, which weakens precision.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context: use this for automatic web-app analysis, and use wopee_create_blank_suite instead when populating a suite manually. The main gap is that it does not explain when to use the rerun parameter versus a fresh dispatch, despite rerun being part of the input schema.

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

Deploy Server

Other Tools