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

Ask an audience

mimiq.ask_audience

Ask simulated people a multiple-choice question (2 to 10 options) and get each person's pick and reasoning. Use it for naming, positioning, or which feature to build next. Each person answers on their own.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No	How many simulated people (default 10, max 50).
`context`	No	What the question is for.	Product validation survey
`options`	Yes	Answer options (2 to 10).
`audience`	Yes	Who to ask, e.g. "SaaS founders with 10 to 50 employees".
`question`	Yes	The question.
`concurrency`	No	Parallel workers (default 6).
`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"
+}

Changed6 schema fields changedSep 24, 2026

changedInput schema / properties / audience / description

Previous value: -"Who to survey. E.g. \"SaaS founders with 10-50 employees\" or \"mobile gamers aged 18-25\"."New value: +"Who to ask, e.g. \"SaaS founders with 10 to 50 employees\"."

changedInput schema / properties / concurrency / description

Previous value: -"Number of parallel survey workers (default 6). Higher values return results faster but may hit rate limits."New value: +"Parallel workers (default 6)."

changedInput schema / properties / context / description

Previous value: -"Additional context about the survey purpose."New value: +"What the question is for."

changedInput schema / properties / count / description

Previous value: -"Number of respondents (default 10, max 50)."New value: +"How many simulated people (default 10, max 50)."

changedInput schema / properties / options / description

Previous value: -"Answer options (2-10 choices)."New value: +"Answer options (2 to 10)."

changedInput schema / properties / question / description

Previous value: -"The survey question to ask."New value: +"The question."

Changed4 schema fields changedMar 17, 2026

addedInput schema / properties / audience / maxLength
```
Added value: +500
```

changedInput schema / properties / concurrency / description

Previous value: -"Parallel survey workers (default 6)."New value: +"Number of parallel survey workers (default 6). Higher values return results faster but may hit rate limits."

addedInput schema / properties / context / maxLength
```
Added value: +500
```

addedInput schema / properties / timeout_seconds

Added value: +{
+  "default": 300,
+  "maximum": 900,
+  "minimum": 30,
+  "type": "integer"
+}

First observedMar 15, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description adds that "each person answers on their own" (independent, and implicitly variable per run), but omits cost, runtime, and non-determinism caveats relevant to a non-idempotent generation call.

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?

Three short sentences, front-loaded with the core action and format, then use cases. The final sentence ("Each person answers on their own") is marginally redundant but does carry the independence point.

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?

With an output schema present, return values need not be explained, and 86% of parameters are self-documented. The description covers purpose and use cases adequately, though it says nothing about the cost/latency profile of a 300s-default, up-to-50-person generation call.

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 86%, so the schema documents audience, count, options, concurrency, and timeout. The description only restates the 2-to-10 options constraint already in the schema and adds no new parameter meaning. Baseline 3 is appropriate.

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?

States a specific verb and resource ("ask simulated people a multiple-choice question") plus the returned artifacts (each person's pick and reasoning). It is distinguishable from siblings like test_copy or compare_copy, though it never explicitly names an alternative to contrast against.

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 concrete when-to-use contexts ("naming, positioning, or which feature to build next"), which is stronger than implied usage. It offers no exclusions or sibling routing, but the use cases are clear and relevant.

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.