Skip to main content
Glama

문서 표 조회

hwp_table_view
Read-only

Retrieve table structure and cell data from HWP/HWPX documents, including row and column sizes, merge details, cell coordinates, and text; select a specific table by index.

Instructions

문서 내 표(Table)의 행/열 크기, 병합 정보, 각 셀의 좌표(row, col) 및 텍스트를 반환합니다. table_index(0부터 시작)로 특정 표만 조회할 수 있습니다. 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_table_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordNo
file_pathYes
table_indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 by structured data. The description adds valuable return-content disclosure (sizes, merges, coordinates, cell text), which matters because there is no output schema, but it says nothing about what happens when the document has no tables, whether table_index out of range errors, or whether password-protected files are supported.

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

Conciseness4/5

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

Three tight sentences with no filler, and the most important information — what comes back — is front-loaded before the parameter hints. Slight structural looseness in moving from return values to two unrelated parameter notes, but nothing is wasted.

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

Completeness4/5

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

For a read-only, non-open-world tool with no output schema, the description adequately covers the return shape, which is the main gap structured data leaves. It is only partially complete on the password parameter and on failure or empty-table behavior, which keeps it out of the top band.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It does explain table_index as 0-based and recommends an absolute file_path, which is real added value. However, the password parameter receives no mention at all, leaving one of three parameters completely undocumented in both schema and description.

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 opens with a specific verb-plus-resource statement: it returns a table's row/column sizes, merge information, each cell's (row, col) coordinates, and cell text. That is far more concrete than the title '문서 표 조회'. It does not explicitly distinguish itself from read-oriented siblings like hwp_get_text, so it falls 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 rather than stated: an agent can infer this is the tool for structured table extraction when plain text extraction is insufficient. The description explains how to target a single table with table_index (0-based), but never says when to prefer hwp_get_text or hwp_search instead, and gives no exclusion conditions.

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