Skip to main content
Glama
Sign In
Mimicus

Mimicus

by qwzx4893-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mimicus_capture_view

Return an actual viewport or bounded region as MCP image content. Optional waitForReadyMs observes transient loading for up to 5000ms without dismissing gates; readinessWait reports the measured outcome.

Instructions

Return an actual viewport or bounded region as MCP image content. Optional waitForReadyMs observes transient loading for up to 5000ms without dismissing gates; readinessWait reports the measured outcome. No persistent screenshot file is created.

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_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorNo
sessionIdYes
waitForReadyMsNo

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / waitForReadyMs
      Added value: +{
+  "default": 0,
+  "maximum": 5000,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv0.3.0-beta.2

TDQS

A3.5/5.0
Behavior4/5

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

The annotations cover the safety side (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds real behavioral detail on top: no persistent screenshot file is written, gates are not dismissed during the wait, and readinessWait reports the measured outcome. It only stops short of saying what happens when readiness is not reached.

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 tight sentences, and the core capability comes first. The wait semantics and the no-file caveat are secondary details placed correctly after the heading sentence. Nothing feels padded.

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?

Since an output schema exists, the description does not need to explain return values. It still mentions readinessWait, which is a useful hint. The missing piece is selector and sessionId semantics, which leaves a gap on a tool with 0% schema coverage.

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 0%, so the description should carry the weight here. It explains waitForReadyMs well, saying it observes transient loading and does not dismiss gates. It says nothing about selector (what a bounded region means, whether it is CSS) or sessionId, so two of the three parameters are still undocumented.

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 precise verb and resource: return the actual viewport or a bounded region as MCP image content. That sets it apart from the motion-capture sibling, but it never names mimicus_capture_motion or mimicus_preview_references directly, so the agent must infer the difference.

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 description says nothing about when to reach for this tool instead of mimicus_capture_motion, mimicus_preview_references, or mimicus_explore_page. It also leaves out prerequisites such as needing an open session. Whoever reads it is left to figure out the selection rules alone.

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