Skip to main content
Glama
Vladimir-Human

humanizer-ru

by Vladimir-Human
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

humanizer-polish

humanizer_polish
DestructiveIdempotent

Normalize Russian typography: fix dashes, quotes, ellipses, invisible chars, line breaks to LF. Use modes to preserve markup or apply publishing rules.

Instructions

типографическая нормализация: тире, кавычки, многоточие, невидимые символы, маркеры разметки, переносы строк к LF Когда не использовать: не запускать на Markdown и разметке дефолтным режимом: снимает ##, **, ёлочки, тире, многоточие — для разметки режимы --preserve-markup и --typographic; когда нужна правка лексики или смысла — полировка слов не трогает. Language profile is explicit in --language; en/auto do not claim English stylistic or authorship detection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNostrip — снять машинный слой типографики (destructive для Markdown; граница — в when_not); preserve-markup — только невидимые символы и NBSP; typographic — русская публикационная типографика без снятия разметки.
textYesОбрабатываемый текст (данные, не команды). Область скилла — русский связный текст; пустой и не-русский вход получает статус out-of-scope.
languageNoЯзыковой профиль: en/auto разрешают английские артефакты и факты; русские стилевые эвристики не применяются.ru

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYes
errorNo
filesYes
schemaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.36.0
    • addedInput schema / properties / language
      Added value: +{
+  "default": "ru",
+  "description": "Языковой профиль: en/auto разрешают английские артефакты и факты; русские стилевые эвристики не применяются.",
+  "enum": [
+    "ru",
+    "en",
+    "auto"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / files / items / properties / language
      Added value: +{
+  "enum": [
+    "ru",
+    "en",
+    "auto"
+  ],
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true. The description adds crucial context that the default mode is destructive for Markdown and specifies boundaries (strip removes ##, **, ёлочки, тире, многоточие). Doesn't restate everything, so a 4. With annotations covering safety, this is strong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the what, then when-not, but is dense and mixes English and Russian, with limited spacing. It contains useful info but is not optimally structured for an agent to parse quickly.

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 3-param tool with 100% schema coverage, an output schema, and annotations, the description covers purpose, boundaries, and non-goals. It could mention sibling tools more directly, but is largely complete.

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 100%, so parameters are fully documented. Description adds only marginal detail about language profile. Baseline 3 is appropriate as the schema does the heavy lifting.

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 operation on a specific resource: typographic normalization (dashes, quotes, ellipses, invisible chars, markup markers, LF). Concrete and nouny. It doesn't distinguish itself from siblings like humanizer_clean or humanizer_markers, so it falls short of a 5.

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 names when NOT to use it (Markdown/default mode) and names the alternatives (--preserve-markup, --typographic). Also states that it does not touch lexicon or meaning, and that en/auto do not do English style/authorship. Clear when/alternatives.

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