Skip to main content
Glama

스냅샷 히스토리 조회

hwp_history
Read-only

Lists SafeWriter snapshot history for an HWP/HWPX document in newest-first order, helping you inspect available restore points before reverting edits.

Instructions

문서의 SafeWriter 스냅샷 히스토리(.hwp-mcp-history) 목록을 최신순으로 조회합니다. 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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 genuine context beyond them — where snapshots live (.hwp-mcp-history) and that results are newest-first — but says nothing about what happens when no history exists or what the entries contain.

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 short sentences with zero padding; the core purpose and ordering are front-loaded, and the path-format note follows as a secondary hint.

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?

No output schema exists, yet the description still conveys that the return is a newest-first list of snapshot entries. The only real gap is the unresolved meaning of file_path, which is a modest omission for a one-parameter read tool.

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 coverage is 0%, so the description must carry the single parameter's meaning. It does add one useful rule ('절대 경로 권장'), but leaves ambiguous whether file_path points at the document or at the history directory/file, which is the key ambiguity for this tool.

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 names a specific verb (조회합니다 / list) and a specific resource (SafeWriter 스냅샷 히스토리, stored in .hwp-mcp-history), and adds the ordering (최신순). That is enough to distinguish it from mutation siblings such as hwp_restore, though it does not name that sibling explicitly.

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 only implied: the read-only listing nature makes the natural workflow (list snapshots, then restore/diff one) inferable, but the description never states when to use this tool versus hwp_restore or hwp_diff, nor any prerequisites or exclusions.

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