Skip to main content
Glama

문서 정보 조회

hwp_info
Read-only

Retrieves HWP/HWPX document metadata—format, page and paragraph counts, fonts, and SHA-256 hash—to verify file details before edits.

Instructions

HWP/HWPX 문서의 메타데이터(형식, 페이지 수, 문단 수, 글꼴, SHA-256 해시 등)를 조회합니다. 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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordNo
file_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 safety and locality are covered. The description earns credit for listing the returned metadata fields, which matters because there is no output schema, but it says nothing about encrypted/password-protected documents, failure behavior, or performance on large files.

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?

Two sentences with zero filler. The core purpose and the returned-field list come first, and the path recommendation follows as a short operational note.

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 two-parameter read-only introspection tool with annotations covering its safety profile, the definition is nearly sufficient: purpose and return contents are clear without an output schema. The remaining gap is the undocumented password parameter and the absence of any note on protected files.

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 the load: it documents file_path semantics ('absolute path recommended'), which is genuine added value. However, the password parameter is never mentioned, leaving the agent unaware that encrypted documents can be opened and how the argument interacts with the required path.

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 gives a specific verb (조회합니다 / retrieve) and resource (HWP/HWPX document metadata) and enumerates what the metadata includes — format, page count, paragraph count, fonts, SHA-256 hash. That enumeration makes it clearly distinct from siblings like hwp_get_text or hwp_search, though no sibling is named explicitly.

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 when-to-use or when-not guidance: nothing tells the agent to prefer this over hwp_get_text when it only needs a document summary, or that it should be called before other operations on an unknown file. The only practical hint, 'absolute path recommended,' is parameter advice rather than selection guidance.

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