Skip to main content
Glama
suthio

Redash MCP Server

by suthio

update_chart_visualization

Update visualization options for a Redash chart, merging new settings with existing configuration.

Instructions

Update chart-specific visualization options and merge them with the current Redash chart config by default

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the visualization
typeNoType of visualization
sortXNoSort the X axis
sortYNoSort heatmap values
xAxisNoX axis settings
yAxisNoY axis settings
legendNoLegend settings
seriesNoSeries-wide chart settings
error_yNoError bar settings
piesortNoSort pie slices
reverseYNoReverse heatmap order
sizemodeNoBubble size mode
directionNoPie chart direction settings
lineShapeNoLine interpolation
enableLinkNoEnable click-through links
linkFormatNoClick-through URL template
showpointsNoShow all points for box charts
textFormatNoData label template
coefficientNoBubble size coefficient
descriptionNoDescription of the visualization
swappedAxesNoSwap the chart axes
chartOptionsNoRaw Redash chart options to merge into the payload
color_schemeNoColor palette name
numberFormatNoNumber format
columnMappingNoColumn mappings such as x, y, and series
percentFormatNoPercent format
seriesOptionsNoPer-series settings keyed by series name
valuesOptionsNoPer-value settings
dateTimeFormatNoDate/time format
linkOpenNewTabNoOpen click-through links in a new tab
replaceOptionsNoReplace the entire options payload instead of merging with the current config
showDataLabelsNoToggle data labels
visualizationIdYesID of the visualization to update
alignYAxesAtZeroNoAlign left and right Y axes at zero
globalSeriesTypeNoChart type
missingValuesAsZeroNoConvert missing values to zero
Behavior2/5

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

No annotations provided, so description carries full burden. It indicates a mutation (update) and default merge behavior, but fails to disclose destructive potential, side effects, auth requirements, or rate limits. Minimal behavioral context.

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?

Single sentence, no fluff. Front-loads the core action and key behavior. Every word earns its place.

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 36 parameters, no output schema, and no annotations, a one-sentence description is insufficient. It does not explain the merge mechanism, the effect of replaceOptions, or the significance of visualizationId. Lacks depth for a complex tool.

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?

Schema has 100% description coverage, so baseline is 3. The description adds a hint about merging behavior but does not elaborate on individual parameters beyond what the schema already provides.

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 verb 'update', the resource 'chart-specific visualization options', and the key behavior 'merge with current config by default'. It distinguishes from siblings like update_visualization by specifying chart-specific.

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 like update_visualization. No prerequisites, exclusions, or context provided. The description only implies usage context via 'chart-specific'.

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/suthio/redash-mcp'

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