Skip to main content
Glama
Sign In
Redash MCP Server

Redash MCP Server

by suthio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_visualization

Create a new visualization for a query by specifying type, name, and configuration options.

Instructions

Create a new visualization for a query

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": {
      "query_id": "<query_id>",
      "type": "<type>",
      "name": "<name>",
      "options": "<options>"
    },
    "name": "create_visualization"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the visualization
typeYesType of visualization. Available types depend on your Redash instance. Use get_query to see existing visualization types in use.
optionsYesVisualization-specific configuration. The structure depends on your Redash instance and visualization type. Use get_visualization to examine existing visualizations of the same type as a reference.
query_idYesID of the query to create visualization for
descriptionNoDescription of the visualization

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • addedInput schema / properties / options / additionalProperties
      Added value: +true
  2. First observedv0.0.13

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It merely states 'Create a new visualization' without disclosing side effects, permission requirements, idempotency, or what happens to the underlying query. This is insufficient for a 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.

Conciseness4/5

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

The description is a single sentence of 7 words, which is very concise. However, it could benefit from additional structure or information without becoming verbose. Score reflects efficiency but also minimal utility.

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?

Despite having 5 parameters, nested objects, and no output schema, the description is extremely brief. It does not explain the concept of a visualization, what is returned after creation, or how it relates to other tools (e.g., get_visualization). The description is inadequate for the tool's complexity.

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 description coverage is 100%, and the schema itself provides detailed parameter descriptions (e.g., how to determine available types and options configurations). The tool description adds no parameter information, so baseline 3 is appropriate.

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 'Create' and the resource 'visualization for a query', distinguishing it from sibling tools like create_query, create_dashboard, and update_visualization. It is specific and unambiguous.

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 description provides no guidance on when to use this tool versus alternatives such as update_visualization or delete_visualization. No prerequisites, context, or exclusions are mentioned.

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