Skip to main content
Glama
nometalalchemist

KitchenSink4Word

by nometalalchemist
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

format_text

Apply character formatting (bold, italic, color, highlight) or change text case to upper, lower, title, or sentence. Target specific text by range or search in Word docs to fix formatting issues.

Instructions

Apply character formatting or change case on a text range. formatting: bold, italic, underline, strike, font, size_pt, color, highlight, small_caps, char_spacing_pt, language, east_asian_language, and more. case: upper | lower | title | sentence. Target: range={start,end}, find, or both; one of formatting or case per call. Auto-backup in file mode (backup=False skips rotation); atomic validated save. Formatting goes live on open documents (serialized); case is file-mode only. For batches, use apply_edits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseNo
findNo
liveNoauto
rangeNo
backupNo
file_pathYes
formattingNo
occurrenceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changedv2.0.0
    • addedInput schema / properties / case
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • removedInput schema / properties / formatting / additionalProperties
      Removed value: -true
    • addedInput schema / properties / formatting / anyOf
      Added value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / formatting / default
      Added value: +null
    • removedInput schema / properties / formatting / type
      Removed value: -"object"
    • addedInput schema / properties / occurrence / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / occurrence / default
      Previous value: -1New value: +null
    • removedInput schema / properties / occurrence / type
      Removed value: -"integer"
    • removedInput schema / properties / paragraph_index
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • addedInput schema / properties / range
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • changedInput schema / required
      Previous value: -[
-  "file_path",
-  "formatting"
-]New value: +[
+  "file_path"
+]
  2. Changed1 schema field changedv1.6.1
    • addedInput schema / properties / live
      Added value: +{
+  "default": "auto",
+  "type": "string"
+}
  3. First observedv1.2.1

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well. It discloses auto-backup behavior and backup=False rotation skipping, atomic validated save, live vs file-mode behavior, and the one-operation-per-call constraint. These are exactly the behavioral traits an agent needs beyond the schema.

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 dense but efficient, front-loading the core purpose before diving into options. It is slightly run-on, but every clause adds useful information and there is no filler.

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 tool with 8 parameters and no annotations, the description covers the key selection, formatting/case values, backup behavior, atomicity, live behavior, and batch routing. Minor gaps around 'live' and 'occurrence' semantics prevent a 5, but the definition is still robust enough for correct invocation in most cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, and it does substantially: it enumerates formatting keys, case enum values, range/find targeting, and the exclusive formatting/case rule. However, it leaves 'live' and 'occurrence' semantics under-explained, so parameter coverage is not complete.

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 opens with a specific verb and resource: 'Apply character formatting or change case on a text range.' It enumerates formatting options and case modes, and is distinct from siblings like set_paragraph_format and apply_style by clearly targeting character-level formatting on a text range.

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

Usage Guidelines4/5

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

The description provides clear usage context: 'Formatting goes live on open documents (serialized); case is file-mode only' and explicitly routes batch work to apply_edits. It does not explicitly contrast with set_paragraph_format or apply_style, but the character-level scope makes the intended use reasonably clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nometalalchemist/KitchenSink4Word'

If you have feedback or need assistance with the MCP directory API, please join our Discord server