wps_word_delete_selection
Delete the currently selected text in a live Word document. Removes highlighted content using the document's object model API.
Instructions
删除当前选中的文字。
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Delete the currently selected text in a live Word document. Removes highlighted content using the document's object model API.
删除当前选中的文字。
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must disclose behavioral traits such as whether the deletion is undoable, destructive to the selection, or if it affects formatting. The single phrase '删除当前选中的文字' lacks such detail, leaving the agent uninformed about side effects.
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 extremely concise: one short sentence that directly states the action. Every word is functional; there is no verbosity or waste.
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?
Given the simplicity of the tool (zero parameters, no output schema), the description is minimal. However, it lacks any mention of return behavior, whether the action is reversible, or what happens when there is no selection. A more complete description would include these contextual details.
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 input schema has zero parameters and 100% schema coverage, so no parameter description is needed. The baseline of 3 applies—the description does not need to add parameter semantics.
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 clearly states the tool deletes selected text in a WPS Word document. It does not explicitly distinguish itself from siblings like `wps_word_replace`, but the specific verb 'delete' and reference to 'selection' make it unambiguous among nearby tools.
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?
No guidance is provided on when to use this tool versus alternatives such as `wps_word_replace` or `wps_word_clear_range` (if it existed). The description does not mention prerequisites like ensuring text is selected, nor when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Antares422/draftly-wps'
If you have feedback or need assistance with the MCP directory API, please join our Discord server