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

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_paragraph_shading

Apply background shading to a paragraph using fill color and optional pattern. Specify the paragraph ID and fill color as a 6-digit hex code.

Instructions

Set background shading on a paragraph.

Args: para_id: paraId of the target paragraph. fill_color: Fill color as 6-digit hex (e.g., "FFFF00"). pattern: Shading pattern (default "clear").

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>",
      "fill_color": "<fill_color>"
    },
    "name": "set_paragraph_shading"
  }
}

Input Schema

NameRequiredDescriptionDefault
para_idYes
patternNoclear
fill_colorYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It fails to disclose potential side effects (e.g., overwriting existing shading), error handling for invalid para_id, or whether it requires specific permissions. The description is minimal and lacks transparency.

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 very concise with three short lines. It front-loads the purpose and lists parameters. However, it restates schema fields without adding much new information, which slightly reduces conciseness efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations and output schema in the context, the description should compensate. It does not describe the return value (e.g., success/failure), nor does it provide enough behavioral context for a mutation tool. The description feels incomplete for safe invocation.

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?

With 0% schema description coverage, the description adds basic meaning: para_id is the target, fill_color is a 6-digit hex example, pattern has a default. However, it does not enumerate possible pattern values or specify the exact format requirements beyond the example, leaving ambiguity.

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 sets background shading on a paragraph, with a specific verb ('set') and resource ('paragraph shading'). This distinguishes it from sibling tools like set_cell_shading, which operate on different elements.

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 you want to add background shading to a paragraph, but provides no guidance on when not to use it or alternatives (e.g., set_cell_shading). The context is implied rather than explicit.

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