Skip to main content
Glama
Sign In
Hangeul-mcp

Hangeul-mcp

by pblsketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_text

Counts plain-text matches per cell in HWP/HWPX files when operating in file mode.

Instructions

Count plain-text matches per cell in FILE MODE; for edit-ready structural addresses use find_text_occurrences.

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": {
      "path": "<path>",
      "query": "<query>"
    },
    "name": "find_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates the tool operates in FILE MODE and counts matches, implying read-only behavior, but does not explicitly state side effects, permissions, or error conditions. Partial disclosure but not comprehensive.

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?

Single sentence that is front-loaded with the purpose. No wasted words; every part is meaningful.

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

Completeness3/5

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

An output schema exists (not shown), so return values are presumably covered. However, the description lacks explanation of 'FILE MODE' and how the count is returned (per cell or aggregate). With two parameters and no schema descriptions, the context feels slightly incomplete.

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 compensate. It implicitly references path and query but adds minimal detail beyond the parameter names. No format, constraints, or usage examples are provided, leaving ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool counts plain-text matches per cell in FILE MODE, using a specific verb and resource. It also distinguishes from the sibling tool find_text_occurrences by specifying the use case for structural addresses.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use this tool (FILE MODE) and when to use an alternative (find_text_occurrences for structural addresses), providing direct guidance.

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

Deploy Server

Other Tools