Skip to main content
Glama
questdb

mcp-server-questdb

Official
by questdb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_cell_dimensions

Resize a QuestDB notebook cell's editor and result panes with CSS pixel heights and set its view, preserving or resetting dimensions as needed.

Instructions

Resize a cell using semantic pane dimensions in CSS pixels and choose its pane view. Every input field is required by strict tool calling: pass null to preserve the current setting. Pass "auto" for a height to restore automatic sizing, or a number to pin it. For SQL/draw cells, view accepts editor, result, or editor_result. view "editor" is DESTRUCTIVE: it discards the cell's result and snapshot and clears its presented mode — the same gesture as toggling off the table or chart in the UI; the response then carries mode:null and result_discarded:true. The stored result/editor_result arrangement is kept for the next result. A cell with nothing to show reports view "editor" and mode null. Markdown has no pane-view state: it reports view, mode, and result_height as null; editor_height sizes its rendered content, while result_height and view are ignored — keep them null. Use 86px for a polished markdown title. Chart result_height must be at least 296px; table results at least 100px. No pane may exceed 2400px.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewYesThe cell's pane view. Null preserves. result and editor_result store the arrangement. editor DISCARDS the cell's result and snapshot, clears its presented mode, and hides the result pane (the toggle-off gesture); on a cell with nothing to show it is a no-op.
cell_idYes
buffer_idYes
editor_heightYesEditor pane height in CSS pixels; for markdown, rendered content height. Null preserves, "auto" restores content-driven sizing. SQL editors are at least 72px, markdown at least 56px, and every pane at most 2400px. Use 86px for a polished markdown title.
result_heightYesResult/chart pane height in CSS pixels. Null preserves, "auto" restores result-driven sizing. Maximum 2400px.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly: it flags view="editor" as destructive, explains that it discards result and snapshot, clears presented mode, and that the response carries mode:null and result_discarded:true, while also noting the markdown no-op/null-reporting behavior.

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?

Front-loads the core action and then layers behavior in a readable progression from general to cell-type-specific. It is dense and a touch long, with some overlap between the height guidance and the schema constraints, but nearly every sentence adds operational value.

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

Completeness5/5

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

No output schema exists, and the description goes further than required by describing the response fields (mode:null, result_discarded:true) and the null-reporting behavior for markdown and empty cells. For a 5-required-param mutation tool with no annotations, this is complete.

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

Parameters5/5

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

Schema coverage is only 60%, but the description compensates heavily: null preserves, "auto" restores content/result-driven sizing, numbers pin, plus cell-type-specific minimums (86px polished markdown title, chart result ≥296px, table ≥100px) and the markdown caveat that result_height and view are ignored.

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?

States a specific verb (resize) and resource (cell) plus the secondary capability of choosing pane view, and uses precise terminology (semantic pane dimensions in CSS pixels) that separates it from siblings like set_cell_layout or set_cell_mode.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear per-context usage rules (SQL/draw cells vs markdown cells, null to preserve, "auto" to restore), which tells the agent when a given argument shape applies. It does not, however, name any alternative sibling tool or state when NOT to use this one, so it stops short of explicit routing guidance.

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