Skip to main content
Glama

Run a workspace's block

execute_workspace
Destructive

Runs a workspace from a specified block server-side. Call once without confirm to preview, then with confirm=true to execute.

Instructions

Executes a workspace starting at the given block (server-side). Powerful: requires confirm=true — first call WITHOUT confirm to preview, then again with confirm:true.

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": "execute_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockIdYes
confirmNoMust be true to execute. Omit/false returns a preview only.
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true; the description adds real context beyond that by labeling the tool 'Powerful' and mandating a two-phase preview-then-confirm flow. It still doesn't say what side effects execution produces or how to interpret the preview, but the safety contract is clearly conveyed.

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?

Two short sentences, front-loaded with the action and immediately followed by the required safety workflow. No filler or redundancy.

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

Completeness3/5

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

For a destructive three-parameter tool with no output schema, the description covers the confirm safety flow but omits permission requirements, what execution returns or how to track it, and the meaning of workspaceId. Adequate to call safely, not complete.

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 only 33%, and only 'confirm' is documented in the schema (consistent with the description). The description usefully reframes blockId as the starting point, but workspaceId carries no explanation at all.

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?

States a specific verb and resource ('Executes a workspace') plus a scoping detail ('starting at the given block') and clarifies execution is server-side rather than local. It does not explicitly distinguish itself from plausible siblings like test_block, which is the main gap.

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

Usage Guidelines4/5

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

Gives concrete invocation guidance: call first without confirm to get a preview, then again with confirm:true. That is an explicit when/how-to-use rule. It stops short of naming alternatives or stating when not to execute (e.g., use test_block for a dry run).

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