Skip to main content
Glama

gridstack_get_cell_height

Retrieve the current height of grid cells to maintain consistent widget sizing and responsive layout alignment in dashboard designs.

Instructions

Get current cell height

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the gridstack_get_cell_height tool. It generates JavaScript code to call grid.getCellHeight() on the GridStack instance and returns it via the utility.
    private async getCellHeight(): Promise<string> {
      return this.utils.generateGridStackCode("getCellHeight", {
        code: `const cellHeight = grid.getCellHeight();`,
      });
    }
  • The input schema and metadata for the tool, registered in listTools(). No input parameters are required.
      name: "gridstack_get_cell_height",
      description: "Get current cell height",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • The tool name registration and dispatch to handler in the callTool switch statement.
    case "gridstack_get_cell_height":
      return this.getCellHeight();
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. It implies a read operation ('get'), but doesn't disclose behavioral traits like whether it requires grid initialization, returns a numeric value or object, has side effects, or handles errors. For a tool with zero annotation coverage, this is a significant gap.

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 a single, efficient sentence with zero waste. It's appropriately sized for a simple getter tool and front-loaded with the core purpose.

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 annotations, no output schema, and a simple purpose, the description is incomplete. It doesn't explain what 'cell' means in the gridstack context, what format the height is returned in (e.g., pixels, units), or any dependencies (e.g., requires an initialized grid). For a tool in a complex sibling set, this leaves gaps.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter semantics, and it correctly implies no inputs are required, earning a baseline score of 4 for this scenario.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get current cell height' clearly states the action (get) and resource (cell height), but it's vague about what 'cell' refers to in the context of gridstack operations. It doesn't distinguish this tool from siblings like 'gridstack_cell_height' (which might set height) or 'gridstack_get_column' (which retrieves column info).

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 is provided on when to use this tool versus alternatives. With siblings like 'gridstack_cell_height' (possibly for setting) and 'gridstack_get_grid_items' (for retrieving other grid properties), the description lacks context about appropriate use cases or prerequisites.

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