Skip to main content
Glama

문서 문자열 검색

hwp_search
Read-only

Search HWP/HWPX documents for a specific string and return its page number, surrounding context, and table-cell coordinates for precise editing.

Instructions

문서 내에서 특정 문자열을 검색하여 페이지 번호, 문맥, 표 셀 좌표를 반환합니다. 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>",
      "query": "<query>"
    },
    "name": "hwp_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
contextNo
passwordNo
file_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 is covered. The description adds genuine value by disclosing the return shape (page number, surrounding context, table cell coordinates), but says nothing about no-match behavior, whether all matches or only the first are returned, or that encrypted documents need a password.

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?

Two compact sentences with the primary capability front-loaded and the path caveat second; nothing is padded. It is efficient, though efficiency here partly reflects under-specification rather than disciplined editing.

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?

With four parameters, zero schema descriptions, and no output schema, the description should do heavier lifting. It covers the return values and the path convention but leaves two parameters undocumented and gives no guidance on result set size or failure modes.

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%, so the description must carry all parameter meaning, yet it only clarifies file_path (absolute path recommended) and implies query. The context (surrounding-text size) and password (presumably for encrypted documents) parameters are left completely unexplained in both structured fields and prose.

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?

States a specific verb (검색) plus resource (문서 내 문자열) and even names the returned artifacts (페이지 번호, 문맥, 표 셀 좌표), so the agent knows exactly what the tool produces. It does not, however, differentiate itself from siblings like hwp_get_text, which an agent could plausibly pick instead.

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?

The description offers no when-to-use or when-not-to-use guidance and never references an alternative such as hwp_get_text or hwp_table_view. Usage must be inferred entirely from the fact that it locates strings.

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