Skip to main content
Glama

截取模拟器画面

wdt_screenshot
Read-only

Captures the current WeChat mini program simulator screen as a PNG and returns the file path. Use it to verify UI state or save visual output during automated testing.

Instructions

截取当前小程序模拟器画面为 PNG。path 省略时写入 MCP output 目录并返回文件路径。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wdt_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoPNG 输出路径

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description does add real behavioral context beyond that — output is PNG and, when path is omitted, the file is written to the MCP output directory and the file path is returned. It stops short of stating failure behavior when no simulator session is active.

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 tight sentences with zero filler, and the core action (capture screen as PNG) is front-loaded ahead of the path-default detail. Nothing is repeated from the title or schema unnecessarily.

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?

For a single-parameter read-only tool with annotations covering safety and no output schema, the description covers format, default output location, and return value. The only gap is preconditions (connected session, simulator readiness), which is a minor omission at this complexity level.

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?

With one parameter at 100% schema coverage, the baseline is 3; the description earns an extra point by explaining the meaning of omission — the default destination directory and the fact that a file path is returned. That is meaning the schema's "PNG 输出路径" does not convey.

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: "截取当前小程序模拟器画面为 PNG" — capture the current mini-program simulator screen as PNG. That is concrete enough to distinguish it from every listed sibling (navigate, evaluate, element, etc.), though it does not explicitly name a sibling it is not.

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

Usage Guidelines3/5

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

Usage is only implied by the wording "当前" (current screen), which hints it should be called after navigating or waiting. There is no explicit when-to-use statement, no prerequisite such as needing a connected/running simulator, and no mention of alternatives for inspecting page state (e.g. wdt_current_page or wdt_page_data).

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