Skip to main content
Glama

Subo

by gg.subo
OverviewDiscussionsAdmin

Replace a script

replace_script

Replace every block of a project's script. Whole-script replace: blocks you leave out are deleted, and block ids change. The project must be inactive. To change one block on a live script, use update_block. Read the subo://guide/authoring resource before writing blocks: block type names, section names and the piping rules are not guessable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blocksYes
project_idYesProject id, from list_projects or create_project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / $defs / ActionConfigSchema / properties / fire_scope / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "respondent",
+      "session"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / $defs / BlockOptionSchema / properties / anchor_position / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "const": "last",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / $defs / ContinueSchema / properties / after / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "pause",
+      "click"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / $defs / ContinueSchema / properties / pause / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / $defs / BlockSchema / properties / text_analysis
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Text Analysis"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior1/5

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

The description explicitly warns that omitted blocks are deleted and block ids change, i.e. it performs destructive updates to existing script data. The annotations declare destructiveHint=false (and idempotentHint=false), which claims only additive behavior. The text and the structured annotation tell the agent opposite things about whether existing data is destroyed.

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?

Four sentences, each load-bearing: action, destructive semantics, precondition + alternative, and authoring prerequisite. Front-loaded with the core purpose and 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 complex mutation tool with no output schema, the description covers preconditions (project inactive), side effects (deletions, id renumbering), the alternative tool, and where to learn the non-guessable block vocabulary. Nothing an agent needs to call it safely and correctly is missing.

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 description coverage is 50%: project_id is documented in the schema, blocks is not. The description compensates by flagging that block type names, section names, and piping rules 'are not guessable' and pointing to an external authoring resource, but it does not itself add per-field meaning for the large nested BlockSchema. Baseline 3 for mid coverage.

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 ('Replace every block of a project's script') and immediately clarifies scope ('Whole-script replace'), which cleanly separates it from the sibling update_block. An agent can distinguish intent from add_block/update_block without opening any 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?

Explicit when-to-use routing: 'To change one block on a live script, use update_block,' plus a hard precondition ('The project must be inactive') and a required prerequisite read ('Read the subo://guide/authoring resource'). Names alternatives, exclusions, and preconditions all at once.

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

All Subo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources