Mimiq: test pages and sign-up flows on simulated people

Compare two pages

mimiq.compare_urls

Compare two web pages (for example a preview deployment and production) on the same simulated people and get Mimiq's call on which to ship. The same people see page A and page B. Mimiq's call combines a forecast, asked in both orders, with how the same people moved: clear, leaning, or too close to call (no pick). Returns the call, the reason in one sentence, how many people moved toward each page, each page's top objections, and a link to the report. Needs public URLs. Without a key, an agent also gets one free A/B test on up to 10 simulated people per version, while the daily free A/B allowance lasts. With a key, any size. On real web page tests the forecast did not beat the simplest guess in a pre-registered run: treat the call as a fast first read.

Input Schema

TableJSON Schema

Name	Required	Description
`count`	No	How many simulated people see both pages (default 10). Use 5 or more: from 5 people up, Mimiq reads who moved.
`url_a`	Yes	Page A, usually the current one (for example production).
`url_b`	Yes	Page B, usually the new one (for example a preview deployment).
`audience`	No	Who the simulated people should be, in plain words, e.g. "startup founders in SF" or "parents shopping for kids toys". If omitted, Mimiq picks the likely audience from the content.
`timeout_seconds`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`run`	No
`call`	No
`tool`	Yes
`status`	No
`report_url`	No
`summary_card`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "call": {
+      "additionalProperties": true,
+      "properties": {
+        "headline": {
+          "type": "string"
+        },
+        "pick": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "reason": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "report_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "run": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "status": {
+      "type": "string"
+    },
+    "summary_card": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool"
+  ],
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: public-URL requirement, the free-tier cap of one A/B test on 10 people per version with a daily allowance, key-based unlimited sizing, and an honest efficacy caveat (the forecast did not beat the simplest guess in a pre-registered run). This rate-limit, auth, and reliability disclosure is exactly the kind of value annotations cannot carry.

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?

Front-loads purpose and mechanism, then progression to returns, requirements, and caveat. It is dense but each sentence carries weight; the enumerated return list is partly redundant given an output schema exists, slightly inflating length.

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

Completeness4/5

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

Given an output schema exists, return values are already covered, and the description still supplies the requirement, quota, auth, and reliability context an agent needs. Only minor gaps remain (e.g., timeout semantics), which the schema already documents, so it is close to complete.

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 80% and parameters are well documented in the schema itself (count, url_a, url_b, audience all have descriptions). The description reinforces the count/people concept and the free-tier 10-person limit but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ("Compare two web pages") with a concrete example (preview deployment vs production) and an explicit mechanism (same simulated people see both). It clearly differentiates from the sibling mimiq.compare_copy by scoping to URLs rather than copy.

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?

Gives clear context for when to use it (comparing a preview against production, needing public URLs) plus auth/quota conditions for with/without a key. It does not explicitly name sibling alternatives like compare_copy or test_page to route the agent, so it falls short of a 5.

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

All Mimiq: test pages and sign-up flows on simulated people tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.