Skip to main content
Glama
Sign In
grp-docx-mcp

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_character_spacing

Adjust the tracking of text in a paragraph run by setting character spacing in points. Specify paragraph ID, run index, and spacing value to expand or condense letters.

Instructions

Set character spacing (tracking) for a specific run in a paragraph.

Args: para_id: paraId of the target paragraph. run_idx: Zero-based index of the run. spacing_pt: Spacing in points (positive = expanded, negative = condensed).

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": {
      "para_id": "<para_id>",
      "run_idx": "<run_idx>",
      "spacing_pt": "<spacing_pt>"
    },
    "name": "set_character_spacing"
  }
}

Input Schema

NameRequiredDescriptionDefault
para_idYes
run_idxYes
spacing_ptYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

A4.3/5.0
Behavior4/5

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

Discloses that spacing_pt in points can expand (positive) or condense (negative) spacing. No annotations provided, so description carries burden; adequately describes effect but omits potential side effects or prerequisites.

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 purpose followed by concise arg list. No fluff, front-loaded, efficient.

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?

Covers core purpose and parameters. Output schema exists (not shown) so return values not needed. Lacks error conditions or preconditions, but acceptable for a simple formatting tool.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so description fully compensates with clear definitions for all three parameters: para_id, run_idx, spacing_pt.

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?

Description clearly states the verb 'Set' and resource 'character spacing (tracking) for a specific run in a paragraph', distinguishing from sibling tools like set_character_position or set_run_font.

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?

No explicit guidance on when to use this tool vs alternatives like set_run_font or set_character_position. Context is implied but no contraindications or when-not-to-use.

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