List all currently open presentations in WPS Office. Use it to identify active slideshows, verify loaded PPT files, or check which presentations are open before performing further actions.
获取当前所有已打开的演示文稿列表。
使用场景：
"有哪些PPT打开着"
"列出所有演示文稿"
"查看打开的PPT"
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0-hardened.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile of this read-only listing operation. The description adds only that it reflects the currently-open state, which is modest extra context, so 3 is appropriate.
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?
Compact and front-loaded with the main statement, followed by three brief usage examples. The examples are slightly redundant but useful, and every sentence earns its place without bloat.
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?
A simple, parameterless, read-only listing tool with annotations covering safety and a clear purpose. It is adequately complete for an agent to call correctly; the only minor gap is not explicitly distinguishing it from wps_get_active_presentation.
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?
The tool has zero parameters, so there is nothing for the description to document. The 0-param baseline of 4 applies and there is no gap to compensate for.
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?
States a specific verb and resource: getting the list of all currently open presentations (演示文稿). It clearly communicates a list operation, which distinguishes it from sibling wps_get_active_presentation (single active doc), though it does not name that sibling explicitly.
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?
Provides three concrete user-query examples ('有哪些PPT打开着', '列出所有演示文稿', '查看打开的PPT') that indicate when to invoke this tool. It gives clear trigger context but does not state when not to use it or name alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.