Mimiq: AI agents use your app like your users and find what breaks

Show a Mimiq report

mimiq.show_report

Read-onlyIdempotent

Show a saved Mimiq run: where it stands while it runs (it waits up to 40 seconds for it to end), then what the agents hit, where each stopped and why, and a link to the full report. Use the session ID from an earlier run or a report URL. Reads your account only and spends no credits.

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": {
      "session_id": "<session_id>"
    },
    "name": "mimiq.show_report"
  }
}

Input Schema

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

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 3, 2026

addedOutput schema / properties / credits

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedOutput schema / properties / findings

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedOutput schema / properties / review

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

Changed1 schema field changedNov 3, 2026

addedOutput schema / properties / versions / items / properties / decisions

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "count": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "label": {
+        "type": "string"
+      },
+      "tone": {
+        "enum": [
+          "good",
+          "bad",
+          ""
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "label",
+      "count",
+      "tone"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

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.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the description only needed to add the non-obvious traits — and it does: a blocking wait of up to 40 seconds, account-scoped reads, and zero credit cost. Those are exactly the operational facts an agent cannot infer from the annotations; the absence of any partial-result note on timeout is a minor gap.

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, then the return content, then the inputs and cost/safety note. Every clause carries information an agent would otherwise have to guess.

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?

An output schema exists, so return shape need not be spelled out, yet the description still summarizes it usefully. The blocking-wait limit and cost/scope note round out a simple two-parameter read tool; the only real hole is the undocumented compare_session_id.

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 0%, so the description must carry parameter meaning, and it only half does: session_id is explained as coming from an earlier run, but compare_session_id is never mentioned at all. The "or a report URL" phrasing also conflicts with the session_id pattern ^[A-Za-z0-9_-]{1,100}$, which no URL would satisfy.

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?

"Show a saved Mimiq run" pairs a specific verb with a specific resource, and the description enumerates what the output contains (run status, per-agent hits, stop reasons, report link). The only sibling, mimiq.test_flow, is not named, so the differentiation is achieved by implication rather than explicit contrast.

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?

"Use the session ID from an earlier run" clearly situates the tool after a run has been created, and the waiting behavior tells the agent this can be polled for status. No explicit exclusion or named alternative is given, and the fallback "or a report URL" is never reconciled with the schema.

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

All Mimiq: AI agents use your app like your users and find what breaks 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.