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

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_cell_shading

Apply fill color as background shading to a cell in a Word table. Specify the table index, row, column, and color.

Instructions

Set background shading fill color on a table cell.

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": {
      "table_idx": "<table_idx>",
      "row_idx": "<row_idx>",
      "col_idx": "<col_idx>",
      "fill_color": "<fill_color>"
    },
    "name": "set_cell_shading"
  }
}

Input Schema

NameRequiredDescriptionDefault
col_idxYes
patternNoclear
row_idxYes
table_idxYes
fill_colorYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

C2.7/5.0
Behavior2/5

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

No annotations provided. The description only states the action; it does not disclose behavioral traits like permissions needed, side effects (e.g., overwriting existing shading), or limitations. The agent is left to assume safe operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, front-loaded and concise. However, it sacrifices necessary detail for brevity, making it adequate but not optimal.

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 tool has 5 parameters with no schema descriptions, the description is too sparse. It does not explain indices, the pattern parameter, or return values despite an output schema existing. The description is incomplete for proper invocation.

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

Parameters1/5

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

With 0% schema description coverage, the description adds minimal parameter meaning. Only 'fill_color' is implied by 'background shading fill color'. Parameters like table_idx, row_idx, col_idx, and pattern are not explained, leaving the agent to guess their roles.

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 action (set), the resource (background shading fill color), and the target (table cell). It distinguishes itself from sibling tools like set_cell_vertical_alignment or set_cell_width.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. No mention of prerequisites or context such as whether the cell must already exist or the table must be selected.

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