Squall Studio

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 or aspect_ratio 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. 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

Name	Required	Description	Default
`patch`	Yes	Fields to change. Send only what you are changing.
`location_id`	Yes	Location id to update.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 7, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description transparently explains side effects: shared locations affect all scenes, editing visual fields marks the location stale, mood/location_type/recurring/appears_in_episodes do not affect the image, and writes are immediate and irreversible.

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?

Though lengthy, every sentence carries critical information—read-before, partial update, shared nature, stale flag, regeneration guidance, and irreversibility. No redundant or vague statements; structure is logical and easy to follow.

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?

The description covers all necessary context for a mutation tool: preconditions (read first), operation semantics (partial update), side effects (shared across scenes, stale flag), and edge cases (when to create new). It is complete even without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema describes location_id and patch, and the patch description clarifies purpose. The description text enumerates all patch fields and explains their effects, so parameter meaning is fully covered despite individual field descriptions being absent.

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 description clearly states the verb 'Overwrite fields on one location' and specifies the resource (location). It distinguishes the tool's behavior from siblings by emphasizing partial updates and the need to read first, making its purpose unambiguous.

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?

Provides explicit usage guidance: read first via get_project_locations or get_location, send only changed fields, and explains when to create a new location instead. Also details the stale-flag consequences for editing certain fields, which is essential for correct use.

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

All Squall Studio tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation4/5

Most tools have clear, distinct purposes, but some overlap exists between get_episode_shots and list_episode_segments, and get_episode_editor vs get_episode could be confused. Overall, the generate/get/list/update families are reasonably distinguishable.

Naming Consistency4/5

The verb_noun pattern is consistently applied across generate_, get_, list_, and update_ tools. Minor deviations like get_episode_editor (which returns a tree rather than an editor) and get_asset_library (rather than list_assets) prevent a perfect score.

Tool Count2/5

With exactly 25 tools, this exceeds the 'too many' threshold of 25+ in the calibration. While the domain is complex, the count feels heavy, especially with many near-duplicate get/list variants.

Completeness2/5

The tool surface is read- and generation-heavy but lacks update operations for characters, episodes, and projects, and has no delete operations at all. This creates notable gaps in lifecycle management, though the existing read/generate coverage is substantial.

Resources

Need Help?