Skip to main content
Glama

Squall Studio

by com.squallstudio
OverviewDiscussionsAdmin

Update location

update_location
Destructive

Overwrite fields on one location. Read it first (get_project_locations or get_location), then send ONLY the fields you changed — omitted fields are left untouched. IMPORTANT: a location is usually shared by several scenes across episodes, so this edit changes every scene that uses it. Check where it is used first; if the change is meant for one scene only, it needs a NEW location rather than an edit to this one. Editing name, short_description, visual_prompt, user_prompt, visual_style, aspect_ratio or spatial_layout marks the location stale, because its existing generated image no longer matches the description — regenerate the image if you want them back in sync. Editing mood, location_type, recurring or appears_in_episodes does not affect the image and leaves the stale flag alone. spatial_layout is the set bible: the named zones of the set and the fixed zone and height of each prop. Scenes must draw their spatial_geometry zones from it instead of inventing labels, so correcting it here fixes prop placement for every scene at once. Keep descriptions consistent with the owning character's status and the project's tone. This writes immediately and cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patchYesFields to change. Send only what you are changing.
location_idYesLocation id to update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / patch / properties / spatial_layout
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "layout_summary": {
+          "type": "string"
+        },
+        "props": {
+          "default": [],
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "co_located_with": {
+                "default": [],
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "description": {
+                "type": "string"
+              },
+              "height": {
+                "type": "string"
+              },
+              "id": {
+                "type": "string"
+              },
+              "movable": {
+                "default": false,
+                "type": "boolean"
+              },
+              "name": {
+                "type": "string"
+              },
+              "zone": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "name",
+              "zone",
+              "height",
+              "description"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "zones": {
+          "default": [],
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "adjacent_to": {
+                "default": [],
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "description": {
+                "type": "string"
+              },
+              "id": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "description"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "layout_summary"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already indicate destructiveHint=true, but the description adds critical behavioral detail: the write is immediate and irreversible. It also discloses the stale-flag side effect for image-related fields and explains which fields affect the image and which do not, going well beyond the structured metadata.

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 description is long but every sentence carries operational weight—read-first workflow, shared-scene warning, stale-flag rules, spatial_layout semantics, and irreversibility are all essential. It is structured with important warnings front-loaded, though slightly dense; trimming could improve scannability without losing value.

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 destructive mutation tool with no output schema, the description covers all the context needed for correct invocation: prerequisites, field-specific side effects, shared-entity consequences, and the inability to undo. Nothing critical for calling 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 100% and the patch field already says 'Send only what you are changing,' but the description adds meaning by grouping fields into image-affecting vs. non-image-affecting categories and explaining spatial_layout's role as the 'set bible.' This helps an agent choose the right patch fields without relying solely on raw schema names.

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?

The opening phrase 'Overwrite fields on one location' uses a specific verb and resource, immediately establishing what the tool does. It also distinguishes itself from related tools like get_location and update_shot by emphasizing that this mutates a location shared across scenes, not a shot-specific edit.

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 gives explicit when-to-use guidance: read the location first, send only changed fields, and check usage across scenes before editing. It also names the alternative—creating a NEW location when the change should apply to one scene only—which directly informs tool selection.

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

All Squall Studio 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