Skip to main content
Glama

문서 본문 추출

hwp_get_text
Read-only

Extract body text from HWP/HWPX documents as plain text or Markdown, with optional page selection and character limits for AI workflows.

Instructions

HWP/HWPX 문서의 본문 텍스트를 추출합니다. format='text' 또는 'markdown'을 지원합니다. file_path는 절대 경로 권장.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_path": "<file_path>"
    },
    "name": "hwp_get_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
formatNotext
passwordNo
file_pathYes
max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that two output formats exist and that absolute paths are preferred, but says nothing about encrypted documents despite a password parameter, nor about whether long documents are silently truncated via max_chars.

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?

Three compact sentences with the core action first, then supported formats, then the path constraint. Nothing is redundant or padded.

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?

For a five-parameter tool with zero schema descriptions and no output schema, the definition leaves too much unspecified — encryption handling, pagination/truncation, and what the returned text looks like. The agent can guess the basic call but cannot predict behavior for anything beyond a plain unencrypted file.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, so the description carries the full burden and only partially meets it: it documents format values ('text' or 'markdown') and advises absolute file_path. The page, max_chars, and password parameters get no explanation at all, even though their behavior (page indexing base, truncation semantics, password requirement) is not obvious.

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?

Names a specific verb (추출/extract) and resource (본문 텍스트 of HWP/HWPX documents), so the agent knows this is the text-reading tool rather than the write siblings (hwp_insert_text, hwp_replace_text). It never explicitly contrasts itself with the other read paths (hwp_search, hwp_table_view, hwp_render_page), so it stops short of a 5.

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 implied by the name and the words '본문 텍스트 추출', but there is no explicit when-to-use statement, no exclusions, and no pointer to hwp_search for keyword lookup or hwp_table_view for tabular content. The agent must infer the choice from sibling names alone.

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