Skip to main content
Glama

Update one block

update_block

Edit a single workspace block in place by sending only the fields to change; all other blocks, links, files, and layout stay untouched.

Instructions

Changes ONE block in place. THIS is how you fix a block — do NOT re-send the whole workspace with set_workspace_content to edit one field, and do NOT append a 'v2' block next to a broken one. Send only the fields you're changing: everything else on the block, all other blocks, the links, the code files, the camera and the hand-placed layout are untouched. Send "" to clear a field. Get the blockId from get_workspace_content. Returns the block as it now stands.

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": {
      "workspaceId": "<workspaceId>",
      "blockId": "<blockId>"
    },
    "name": "update_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
iNoGrid column. Omit to leave the block where it is.
jNoGrid row.
codeNoJavaScript for a Process block.
typeNoBlock type. Changing to/from "SignalR" is rejected — replace the content instead.
colorNo
labelNo
blockIdYesThe block's id, as returned by get_workspace_content.
rawDataNoStatic JSON/text for a Raw data / API Endpoint block.
staticFileNoFor an API Endpoint block: a workspace code file served verbatim, no JS executed.
handlerCodeNoFor a "SignalR" block: the C# handler body.
workspaceIdYes
endpointPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a lot: it discloses partial-update semantics (only changed fields sent), what is preserved (other fields, other blocks, links, code files, camera, layout), the empty-string clearing convention, and that the updated block comes back. It does not cover failure modes, permissions, or whether the previous state is recoverable, which keeps it short of a 5.

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-loaded with the core behavior, then the anti-patterns, then the mechanics. The capitalized warnings are emphatic but each sentence conveys a distinct constraint; only the rhetorical "THIS is how you fix a block" is arguably redundant with the sentences around it.

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

Completeness4/5

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

For a 12-parameter mutation tool with no annotations and no output schema, the description supplies the essential mental model: targeted patch, everything else preserved, returns the current block. The remaining gap is that it does not state what a failed or rejected update leaves behind, but the operational picture is otherwise complete.

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?

Schema coverage is 67%, and the description adds real meaning beyond it: the patch/omit convention for unlisted fields, the "" sentinel for clearing a value, and the provenance of blockId. It does not explain the type-change restriction or the less-obvious fields like staticFile and handlerCode, but the schema descriptions cover those.

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?

"Changes ONE block in place" gives a specific verb and resource with explicit scope (single block, in-place), and it immediately distinguishes itself from set_workspace_content and from appending a new block. An agent can tell what this does and what it is not without opening the schema.

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

Usage Guidelines5/5

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

The description names two wrong alternatives explicitly (re-sending the workspace with set_workspace_content, appending a 'v2' block) and states the condition for choosing this tool instead. It also directs the agent to get_workspace_content for the blockId, so the prerequisite step is covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.