Skip to main content
Glama
Sign In
hex-mcp-server

hex-mcp-server

by chuotdelongchamp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hex-update-cell

Update a Hex cell's source code or SQL data connection using its cell ID. Modify existing notebook or SQL cells through the Hex API.

Instructions

Update a cell's source and/or data connection.

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": {
      "cellId": "<cellId>"
    },
    "name": "hex-update-cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
cellIdYes
sourceNoNew cell source content
dataConnectionIdNoData connection UUID for SQL cells

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

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 carries the full burden. It does not disclose required permissions, whether this is a partial update, side effects (e.g., whether changing source re-runs the cell), or reversibility. The 'and/or' phrasing is the only mild signal that fields are optional.

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?

A single tight sentence with the operation front-loaded and no filler. However, the brevity is achieved partly by omitting useful context rather than by efficient phrasing.

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?

For a mutation tool with no annotations, no output schema, and three parameters, the description is too thin. It omits update semantics, side effects, and any return behavior an agent would need before invoking it.

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 coverage is 67%, with the two payload parameters documented in the schema itself. The description adds little beyond the schema, though 'and/or' implies both are optional alongside the required cellId. A baseline 3 is appropriate given the schema does most of the work.

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 states a clear verb (update) and resource (cell) plus which fields are updated (source, data connection). It does not distinguish this tool from the many sibling read/create cell tools (hex-get-cell, hex-create-cell, hex-delete-cell), so it falls short of a 5.

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?

There is no guidance on when to use this over alternatives such as hex-create-cell or hex-edit-collection, and no prerequisites or context for choosing it. It merely restates the operation.

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