cwtwb

by aidatacooper

Overview Schema Source Related Servers Discussions Admin

Python

Local

configure_dual_axis

Configure a dual-axis chart composition.

Instructions

Configure a dual-axis chart composition.

For dual-axis chart patterns and best practices, read: read_resource('cwtwb://skills/chart_builder')

Input Schema

Name	Required	Default
`rows`	No
`size_1`	No
`size_2`	No
`color_1`	No
`color_2`	No
`columns`	No
`filters`	No
`label_1`	No
`label_2`	No
`detail_1`	No
`detail_2`	No
`hide_axes`	No
`sort_field`	No
`color_map_1`	No
`mark_type_1`	No	Bar
`mark_type_2`	No	Line
`show_labels`	No
`mark_color_1`	No
`mark_color_2`	No
`size_value_1`	No
`size_value_2`	No
`synchronized`	No
`wedge_size_1`	No
`wedge_size_2`	No
`hide_zeroline`	No
`reverse_axis_1`	No
`worksheet_name`	Yes
`dual_axis_shelf`	No	rows
`mark_sizing_off`	No
`sort_descending`	No
`table_calc_overrides`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.28.0Oct 12, 2026

addedInput schema / properties / sort_field

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Sort Field"
+}

addedInput schema / properties / table_calc_overrides

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

First observedv0.18.1Apr 22, 2026

TDQS

C2.4/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 disclosure burden for a 31-parameter mutation-style tool. It omits whether the worksheet must already exist, whether existing chart settings are overwritten, what permissions are needed, and whether the change is reversible. It adds almost nothing beyond 'this configures a dual-axis chart.'

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?

Two short sentences, front-loaded with the action, with no filler or redundancy. The second sentence is a routing hint rather than bloat, though it does substitute a pointer for information the description could have supplied.

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

Completeness1/5

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

For a 31-parameter tool with zero schema descriptions, no annotations, and only one required field documented by name, the description is far too thin. The presence of an output schema excuses it from explaining return values, but not from explaining how to drive the input parameters.

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?

Schema description coverage is 0% across 31 parameters, and the description explains none of them. Pairs like size_1/size_2, color_1/color_2, mark_type_1/mark_type_2, dual_axis_shelf, synchronized, and table_calc_overrides are left entirely opaque, so an agent must guess at the axis-1/axis-2 semantics and accepted formats.

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 names a specific verb and resource ('Configure a dual-axis chart composition'), which is enough to tell it is a chart-configuration tool. However, it does not differentiate itself from siblings like configure_chart, configure_layered_chart, or configure_chart_recipe, nor does it say what a 'composition' modifies.

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?

The only guidance is a pointer to a skill resource for 'dual-axis chart patterns and best practices,' which is about how to do it well, not when to choose this tool over configure_chart or configure_layered_chart. No prerequisites, exclusions, or alternative-selection conditions are stated.

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

Deploy Server