Skip to main content
Glama

clear_run_formatting

Remove all character formatting from a specific text run in a Word document, causing it to inherit the default paragraph or style formatting.

Instructions

Remove all character formatting from a run, causing it to inherit paragraph/style defaults.

Args: para_id: paraId of the target paragraph. run_idx: Zero-based index of the run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
para_idYes
run_idxYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It clearly states the tool removes all character formatting and causes inheritance of defaults, which is a transparent behavioral description. However, it does not detail which specific formatting attributes are affected.

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?

The description is concise with three sentences: action statement, blank line, and two argument lines. It is well-structured and efficient, with no redundancy.

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?

While the tool is simple with two parameters, the description does not mention the return value despite an output schema existing. Additionally, it could provide more context about when to use this tool relative to siblings like set_run_color or set_run_font. Overall, it is adequate but lacks some completeness.

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 coverage is 0% with minimal titles. The description adds meaning by explaining that para_id is the paragraph ID and run_idx is a zero-based index, which helps clarify parameter usage beyond the schema.

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 the tool removes all character formatting from a run, which is a specific verb+resource. It also explains the effect (causing inheritance of paragraph/style defaults), distinguishing it from sibling tools like set_run_font or set_run_size.

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 use when resetting formatting, but does not explicitly state when to use versus alternatives like set_* tools. No guidance on when not to use or prerequisites is provided.

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/SecurityRonin/docx-mcp'

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