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

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_character_position

Adjust vertical character position in a Word paragraph run by setting a raised or lowered offset in points.

Instructions

Set vertical character position (raised/lowered) for a specific run.

Args: para_id: paraId of the target paragraph. run_idx: Zero-based index of the run. position_pt: Offset in points (positive = raised, negative = lowered).

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>",
      "position_pt": "<position_pt>"
    },
    "name": "set_character_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
para_idYes
run_idxYes
position_ptYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

A3.7/5.0
Behavior3/5

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

No annotations, so description must disclose behavior. It mentions 'positive = raised, negative = lowered' and effect on specific run, but lacks details on limits, unit confirmation, or side effects on other formatting.

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?

Very concise: three sentences covering purpose, arg format, and sign convention. No unnecessary words.

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?

Covers basic usage but lacks details: expected output format (despite output schema existing), behavior on invalid indices, and range of position_pt.

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 coverage 0%, so description must explain parameters. It does: para_id, run_idx, position_pt each with brief explanation. But no context on how to obtain para_id/run_idx or bounds.

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 states specific verb 'set' and resource 'character position' for a specific run, clearly distinguishing from siblings like set_run_subscript/superscript.

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?

Implies when to use (vertical offset), but no explicit when-not or alternatives. For example, superscript/subscript might be alternatives, but not mentioned.

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