Capture a full-screen PNG and save it to a specified path, or to a temporary directory if none is given. Returns the saved file path for immediate use.
截取全屏 PNG。
Args: path: 保存路径；省略则存到临时目录。
Returns: 保存的文件路径。
| Name | Required | Description | Default |
|---|---|---|---|
| path | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It discloses that the tool captures the entire screen, saves to a specified path or a temporary directory when omitted, and returns the saved file path. Missing minor details like permission requirements or overwite behavior, but core behavior is transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact: one purpose sentence plus short Args and Returns lines. Every sentence earns its place and the main behavior is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one optional parameter and no output schema, the description covers purpose, parameter behavior, and return value. It does not specify naming, overwite, or multi-monitor behavior, but these are minor for the basic use case.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must explain the path parameter. It does: path is the save destination, and omitting it stores the file in a temp directory. This adds meaningful semantic value beyond the bare schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: capture a full-screen PNG screenshot. This clearly distinguishes it from siblings like open_app, open_url, and get_screen_size, which do different things.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The use case is clear: use this when a full-screen PNG capture is needed. It gives context about the optional path and temporary fallback, and there are no competing screenshot tools among the siblings, so explicit exclusions are not necessary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.