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

Show a Mimiq report

mimiq.show_report

Read-onlyIdempotent

Show the finished result of a saved Mimiq test, or two saved tests compared: the call, counts, objections in simulated people's words, and a full report link. Use session IDs from an earlier test result or report URL. Reads your account only and spends no credits.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`session_id`	Yes
`compare_session_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	Yes
`title`	Yes
`reason`	Yes
`status`	No
`headline`	Yes
`progress`	No
`versions`	Yes
`limitation`	Yes
`report_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedOutput schema / properties / progress

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "done": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "total": {
+      "minimum": 1,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "done",
+    "total"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 30, 2026
- addedOutput schema / properties / status
```
Added value: +{
+  "enum": [
+    "finished",
+    "running"
+  ],
+  "type": "string"
+}
```
- changedOutput schema / properties / versions / minItems
```
Previous value: -1New value: +0
```

Changed4 schema fields changedSep 30, 2026

addedOutput schema / properties / versions / items / properties / answers

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "option": {
+        "type": "string"
+      },
+      "person": {
+        "type": "string"
+      },
+      "reason": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "person",
+      "option",
+      "reason"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / versions / items / properties / counts / required

Previous value: -[
-  "total",
-  "stayed",
-  "left"
-]New value: +[
+  "total"
+]

addedOutput schema / properties / versions / items / properties / unanswered
```
Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}
```

addedOutput schema / properties / versions / items / properties / votes

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "count": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "option": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "option",
+      "count"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

AddedSep 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false. The description adds genuinely new context beyond those: 'Reads your account only' (auth scope) and 'spends no credits' (cost profile), which the annotations do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action and its two modes, followed by input provenance and the read-only/no-credit note. No wasted text.

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

Completeness5/5

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

An output schema exists so return values need not be described, and annotations cover the safety profile. The description supplies the remaining essentials (input source, comparison mode, auth scope, cost), leaving nothing an agent needs in order to call it correctly.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the load, and it does add meaning: it explains the provenance of session_id (an earlier result or report URL) and, via 'two saved tests compared', the paired semantics of compare_session_id. It still doesn't state that compare_session_id is optional, so it stops short of full coverage.

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+resource ('Show the finished result of a saved Mimiq test, or two saved tests compared') and enumerates the returned content. This clearly separates it from the sibling test_* creation tools, which all produce new tests rather than retrieve saved ones.

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?

Tells the agent where inputs come from ('session IDs from an earlier test result or report URL') and implies the compare mode by describing the two-session case. It gives clear context but no explicit when-not-to-use or exclusion against siblings.

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.