Skip to main content
Glama
Sign In
Hangeul-mcp

Hangeul-mcp

by pblsketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_and_replace

Find and replace text in a document and write the result to a new file. If multiple matches exist, replace fails unless scope is set to 'all'.

Instructions

One-shot text replace written to a NEW file; fails closed on 2+ matches unless scope='all'.

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>",
      "find": "<find>",
      "replace": "<replace>",
      "out_path": "<out_path>"
    },
    "name": "search_and_replace"
  }
}

Input Schema

NameRequiredDescriptionDefault
findYes
pathYes
scopeNo
replaceYes
out_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool writes to a new file (non-destructive) and fails on multiple matches unless scope='all'. This covers key error behavior and safety, but omits return value or side effects.

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?

The description is a single sentence that is concise and front-loaded with the core action. It could be slightly improved by separating the failure condition, but it is efficient with no wasted words.

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?

Given 5 parameters with no schema descriptions, no annotations, and an output schema (unprovided), the description is incomplete. It fails to explain parameter syntax, return format, or usage context beyond the failure condition, leaving significant gaps for an AI agent.

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 coverage is 0% and the description adds no explicit parameter definitions. It only mentions 'scope' in a condition. For 5 parameters (find, path, replace, out_path, scope), the AI must infer meaning from names alone, which is insufficient.

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 'One-shot text replace written to a NEW file', specifying the action (replace text) and output destination (new file). This distinguishes it from siblings like batch_replace (likely in-place) and find_text (no replace).

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?

The description implies usage via the failure condition 'fails closed on 2+ matches unless scope="all"', guiding when to set scope. However, it does not explicitly compare to alternatives or state when to use this tool over siblings.

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