Skip to main content
Glama
Sign In
Redash MCP Server

Redash MCP Server

by suthio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_widget_layout

Update a dashboard widget's position and size by specifying grid coordinates, column width, row height, and optional auto-height to organize dashboard layout.

Instructions

Move or resize a single widget by updating its grid position

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": {
      "widgetId": "<widgetId>",
      "position": "<position>"
    },
    "name": "update_widget_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionYes
widgetIdYesID of the widget

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It states that the tool moves or resizes, implying mutation, but does not disclose permissions, idempotency, side effects, or error handling. The behavior of partial vs. full position replacement is unclear.

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, front-loaded sentence of 12 words, which is concise. However, it sacrifices valuable context that could be added without becoming verbose.

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 no output schema, no annotations, and nested parameters, the description is incomplete. It does not explain the grid system, constraints, or what happens on success/failure. The tool's mutation aspect and parameter structure are under-described.

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 50% (the 'position' object lacks a description). The description only mentions 'grid position' without elaborating on the sub-fields (col, row, sizeX, sizeY, autoHeight) or their constraints. It fails to add meaning beyond what the schema 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 uses specific verbs 'Move or resize' and identifies the resource 'single widget' and the affected attribute 'grid position'. It clearly distinguishes from sibling tools like 'update_widget', which likely updates other properties.

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 over alternatives, such as 'update_widget' for non-layout changes. No prerequisites or conditions for use 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