Skip to main content
Glama

gridstack_cell_height

Adjust the height of grid cells to customize dashboard layouts, supporting pixel values, CSS units, or automatic sizing.

Instructions

Update cell height

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valNoNew cell height (px, 'auto', 'initial', CSS units)
updateNoUpdate existing widgets

Implementation Reference

  • The handler function that implements the core logic for the 'gridstack_cell_height' tool. It generates the GridStack.js 'cellHeight' method call based on input parameters and uses the GridStackUtils helper to produce executable JavaScript code.
    private async cellHeight(params: CellHeightParams): Promise<string> {
      const { val, update = true } = params;
    
      return this.utils.generateGridStackCode("cellHeight", {
        value: val,
        update,
        code:
          val !== undefined
            ? `grid.cellHeight(${
                typeof val === "string" ? `'${val}'` : val
              }, ${update});`
            : `grid.cellHeight();`,
      });
    }
  • The JSON schema defining the input parameters for the 'gridstack_cell_height' tool: 'val' for the new cell height value and optional 'update' boolean.
    {
      name: "gridstack_cell_height",
      description: "Update cell height",
      inputSchema: {
        type: "object",
        properties: {
          val: {
            oneOf: [{ type: "number" }, { type: "string" }],
            description: "New cell height (px, 'auto', 'initial', CSS units)",
          },
          update: {
            type: "boolean",
            description: "Update existing widgets",
            default: true,
          },
        },
      },
    },
  • The switch case in callTool method that registers and dispatches calls to the specific cellHeight handler for the tool name 'gridstack_cell_height'.
    case "gridstack_cell_height":
      return this.cellHeight(args as CellHeightParams);
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Update cell height' implies a mutation but doesn't specify permissions needed, side effects (e.g., layout changes), error conditions, or response format. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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?

The description is extremely concise at three words, front-loading the core action and resource without any wasted text. It efficiently communicates the essential purpose in a minimal format, earning full marks for brevity and clarity.

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 the tool's mutation nature (implied by 'update'), lack of annotations, and no output schema, the description is insufficient. It doesn't cover behavioral aspects like what 'cell' refers to in the gridstack context, how changes propagate, or what happens on failure. For a tool in a complex sibling set, more context is needed to ensure correct usage.

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%, with clear documentation for both parameters ('val' and 'update'), so the schema does the heavy lifting. The description adds no additional parameter context beyond implying height adjustment, which aligns with but doesn't enhance the schema. This meets the baseline for high schema coverage.

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 'Update cell height' clearly states the action (update) and target resource (cell height), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'gridstack_get_cell_height' or 'gridstack_resize_widget', which would require more specific context about what makes this tool distinct.

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. With siblings like 'gridstack_get_cell_height' (for reading) and 'gridstack_resize_widget' (which might affect height), there's no indication of appropriate contexts, prerequisites, or exclusions for this update operation.

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/raghavsharma-simpplr/gridstack-mcp-server'

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