Skip to main content
Glama
mjyoo2
by mjyoo2

clear_selection

Clear the active text selection in a Hangul (HWP) document, deselecting highlighted text and resetting the editing cursor.

Instructions

Clear the current text selection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It says 'Clear the current text selection' but does not state whether selected content is preserved, whether the cursor moves, or what side effects occur. It also fails to mention that doc_id is needed to identify the target document.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with no filler, which is appropriate. However, it is under-specified to the point of omitting the parameter and usage context, so brevity comes at the expense of usefulness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This tool is relatively simple, but with no annotations, a required doc_id param, and related sibling tools, the description leaves out essential context: which document the selection applies to, whether content is preserved, and how this differs from delete_selection. It is not complete enough for an agent to confidently invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention the required doc_id parameter at all. The only parameter remains entirely undocumented by both the schema and description, so the agent has no semantic guidance beyond the minimal 'Doc Id' title.

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 clear verb and object: 'Clear the current text selection.' The purpose is unambiguous, but it does not differentiate itself from sibling tools like delete_selection, which could plausibly mean removing the selected content, or select_text. The absence of an explicit 'without deleting content' qualifier leaves a small ambiguity.

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?

There is no guidance about when to use this tool versus alternatives such as select_text, get_selection_info, or delete_selection. The description only states what it does, not when or why an agent should prefer it over related selection tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mjyoo2/hwp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server