Skip to main content
Glama

Append a flow to a workspace

add_to_workspace

Appends a new self-contained flow of blocks and links to an existing workspace without altering its current content. Use it to add flows safely; the server assigns non-colliding ids.

Instructions

APPENDS a self-contained flow (new blocks + links among them) to a workspace WITHOUT touching its existing blocks — the SAFE way to add to a workspace that already has content. Unlike set_workspace_content it cannot wipe existing flows and needs no read-modify-write: the server assigns fresh non-colliding ids and lays the new flow out below the existing blocks. Links here may only connect your NEW blocks to each other; to wire INTO an existing block, use get_workspace_content + set_workspace_content instead. Returns the added blocks with their assigned ids + signalRGuid. zones adds new canvas areas alongside the flow; an id that already exists is kept as it is, so appending cannot redefine somebody else's zone either.

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>",
      "blocks": "<blocks>"
    },
    "name": "add_to_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
seoNoHow much to report about the HTML pages being written: "full" (default) everything, "minimal" only what an indexed page cannot do without, "none" to say nothing. Never blocks the write; a page with <meta name="robots" content="noindex"> is exempt either way.
filesNoNew code files to add (existing names are kept, not overwritten).
linksNo
zonesNoNew canvas areas (an id that already exists is kept, not redefined).
blocksYes
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that existing blocks are never touched, that the server assigns fresh non-colliding ids, that new blocks are laid out below existing ones, that existing files and zones are kept rather than overwritten, and that a schedule declaration does not start the schedule (create_schedule is required). It also describes the return value (added blocks with assigned ids and signalRGuid).

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?

The safety claim and the sibling contrast are front-loaded, and the trailing sentences about zones and returns each add information. It is a dense single paragraph with several parenthetical asides, so it is slightly heavier than needed but contains no filler.

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?

For a six-parameter mutation tool with no annotations and no output schema, the description covers the mutation boundary, id assignment, layout, return shape, and the cross-tool follow-up (create_schedule). Nothing an agent needs to call it correctly is missing.

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 only 50%, so the description must add meaning, and it does for the riskiest parameters: `links` may only connect new blocks to each other, and `zones`/`files` entries with colliding ids or names are kept as-is. It repeats a few semantics the schema already states (non-overwrite behavior) and says nothing about `seo` or the block `type` variants, which the schema covers instead.

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 and resource ('APPENDS a self-contained flow ... to a workspace') and immediately scopes it ('new blocks + links among them', 'WITHOUT touching its existing blocks'). It explicitly contrasts with the sibling set_workspace_content, so an agent can distinguish the two without reading either 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?

Gives an explicit when-to-use ('the SAFE way to add to a workspace that already has content') and a when-not plus named alternative for the case it does not cover ('to wire INTO an existing block, use get_workspace_content + set_workspace_content instead'). It also names the alternative it replaces and why (no read-modify-write).

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