Skip to main content
Glama
Sign In
Mimicus

Mimicus

by qwzx4893-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mimicus_capture_motion

Capture a selected effect as actual timestamped images, optionally applying one safe interaction between initial and subsequent frames. No automatic whole-site recording.

Instructions

Capture a selected effect as actual timestamped images, optionally applying one safe interaction between initial and subsequent frames. No automatic whole-site recording.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "mimicus_capture_motion"
  }
}

Input Schema

NameRequiredDescriptionDefault
framesNo
selectorNo
sessionIdYes
intervalMsNo
interactionNo

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • changedInput schema / properties / interaction / properties / action / enum
      Previous value: -[
-  "hover",
-  "click",
-  "focus",
-  "pointer",
-  "scroll",
-  "navigate",
-  "resize",
-  "key",
-  "wait",
-  "touch",
-  "drag"
-]New value: +[
+  "hover",
+  "click",
+  "focus",
+  "pointer",
+  "scroll",
+  "navigate",
+  "resize",
+  "key",
+  "wait",
+  "renew",
+  "touch",
+  "drag"
+]
  2. First observedv0.3.0-beta.2

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, and openWorld=true, so the safety profile is covered. The description usefully adds that output is 'actual timestamped images' and that only one 'safe' interaction is applied, but it never defines what makes an interaction safe or what side effects a click/navigate interaction may have.

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?

Two tight sentences with the core purpose front-loaded and the negative scope statement following. No wasted filler, though the second sentence could have carried parameter context instead of a bare exclusion.

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

Completeness2/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, but for a 5-parameter tool with a rich nested interaction object and zero schema descriptions, the definition is far too thin to let an agent invoke it correctly without opening the schema in detail.

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 description coverage is 0% across 5 parameters, including a nested 12-action interaction object. The description gestures at the interaction parameter ('one safe interaction between initial and subsequent frames') but says nothing about frames, intervalMs, or selector semantics, so it fails to compensate for the coverage gap.

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 states a specific verb (capture) and concrete output (timestamped images of a selected effect), and rules out whole-site recording. It is clear about what it does, but does not distinguish it from the sibling mimicus_capture_view, leaving the boundary between the two capture tools ambiguous.

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

Usage Guidelines2/5

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

The only guidance is the implicit exclusion 'No automatic whole-site recording'; there is no statement of when to choose this over mimicus_capture_view or mimicus_interact, and no prerequisites or session requirements are given.

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