cwtwb

by aidatacooper

Overview Schema Source Related Servers Discussions Admin

Python

Local

configure_worksheet_style

Apply worksheet-level styling: background color, axis/grid/border visibility.

Instructions

Apply worksheet-level styling: background color, axis/grid/border visibility.

pane_mark_style accepts mark-labels-range-field as a public field expression and resolves its native qualified reference for min/max labels.

For formatting best practices, read: read_resource('cwtwb://skills/formatting')

Input Schema

Name	Required	Description	Default
`hide_axes`	No
`map_style`	No
`axis_style`	No
`size_style`	No
`color_style`	No
`cell_formats`	No
`hide_borders`	No
`legend_style`	No
`pane_formats`	No
`hide_reflines`	No
`hide_zeroline`	No
`label_formats`	No
`table_formats`	No
`gridline_style`	No
`header_formats`	No
`hide_droplines`	No
`hide_gridlines`	No
`worksheet_name`	Yes
`disable_tooltip`	No
`hide_band_color`	No
`pane_cell_style`	No
`pane_mark_style`	No
`background_color`	No
`hide_sort_controls`	No
`hide_table_dividers`	No
`pane_datalabel_style`	No
`hide_col_field_labels`	No
`hide_row_field_labels`	No
`pane_trendline_hidden`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.28.0Oct 12, 2026

addedInput schema / properties / color_style

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Color Style"
+}

addedInput schema / properties / gridline_style

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Gridline Style"
+}

addedInput schema / properties / hide_sort_controls

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Hide Sort Controls"
+}

addedInput schema / properties / legend_style

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Legend Style"
+}

addedInput schema / properties / map_style

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Map Style"
+}

addedInput schema / properties / pane_formats

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Pane Formats"
+}

addedInput schema / properties / size_style

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Size Style"
+}

addedInput schema / properties / table_formats

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Table Formats"
+}

First observedv0.18.1Apr 22, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses one behavioral quirk (pane_mark_style resolving native qualified references), but says nothing about whether styling overwrites existing settings, permissions required, reversibility, or scope of effect for a 29-parameter mutation tool.

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 purpose is front-loaded and the three blocks are short, but the middle sentence about pane_mark_style is an oddly narrow detail given the much larger undocumented surface, making the structure feel unbalanced rather than optimally prioritized.

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?

With 29 parameters, 0% schema coverage, no annotations, and only a required worksheet_name plus an output schema, the description is far too thin to guide correct invocation. It covers a handful of style categories and one parameter quirk, leaving the agent to guess at the rest.

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

Parameters2/5

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

Schema description coverage is 0% across 29 parameters, so the description must compensate but barely does. It mentions only background color, the axis/grid/border visibility flags collectively, and one specific parameter (pane_mark_style), leaving the vast majority of parameters (map_style, legend_style, cell_formats, etc.) undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Apply worksheet-level styling') and enumerates the style categories (background color, axis/grid/border visibility). This is distinguishable from siblings like set_field_format or set_worksheet_title. It stops short of explicitly naming an alternative tool, so it doesn't reach 5.

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?

There is no explicit when-to-use or when-not guidance and no routing to alternatives among the many style-related siblings (set_field_format, set_shape_palette, add_reference_band). The only pointer is a formatting best-practices resource, which is not usage selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server