Galatic.ai

Save flow

save_flow

Create a Flow Studio flow (no flowId; name required) and get { flowId, version }, or update one of the user's flows (404 otherwise) and get the new version. On update, nodes, edges, characters and voices each replace the stored array when passed and are kept when omitted. nodes and edges must form a graph with no cycle (400). aspectRatio is "16:9" or "9:16"; visualStyle at most 600 characters; seasons up to 99 of { number 1-99, title, blurb }; executionMode "step-functions" (default) or "bedrock-flows". Spends no credits; use run_flow to run it. A flow with characters and seasons is a series for the episode tools.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "save_flow"
  }
}

Input Schema

Name	Required	Description
`name`	No	Required to create.
`edges`	No	Replaces all edges; must not form a cycle.
`nodes`	No	Replaces all nodes.
`flowId`	No	From list_flows. Omit to create.
`voices`	No	Replaces the list.
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`seasons`	No	Up to 99 of { number 1-99, title, blurb }.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`characters`	No	Series cast; replaces the list.
`aspectRatio`	No	"16:9" or "9:16".
`description`	No
`visualStyle`	No	At most 600 characters.
`executionMode`	No	"step-functions" (default) or "bedrock-flows".
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 27, 2026
- addedInput schema / properties / aspectRatio / description
```
Added value: +"\"16:9\" or \"9:16\"."
```
- addedInput schema / properties / characters / description
```
Added value: +"Series cast; replaces the list."
```
- addedInput schema / properties / edges / description
```
Added value: +"Replaces all edges; must not form a cycle."
```
- addedInput schema / properties / executionMode / description
```
Added value: +"\"step-functions\" (default) or \"bedrock-flows\"."
```
- addedInput schema / properties / flowId / description
```
Added value: +"From list_flows. Omit to create."
```
- addedInput schema / properties / name / description
```
Added value: +"Required to create."
```
- addedInput schema / properties / nodes / description
```
Added value: +"Replaces all nodes."
```
- addedInput schema / properties / seasons / description
```
Added value: +"Up to 99 of { number 1-99, title, blurb }."
```
- addedInput schema / properties / visualStyle / description
```
Added value: +"At most 600 characters."
```
- addedInput schema / properties / voices / description
```
Added value: +"Replaces the list."
```
First observedOct 24, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already indicate this is a non-read-only, non-destructive, non-idempotent operation, and the description adds meaningful behavioral detail beyond them. It explains replacement semantics for nodes, edges, characters, and voices, cycle validation with 400, credit usage, and the create/update distinction.

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?

The description is dense but front-loaded around the primary create/update behavior. Despite covering many parameters and constraints, each sentence adds operational value and avoids repetition.

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 14-parameter mutation tool with no output schema, the description is remarkably complete: it explains create versus update, return values, replacement behavior, validation constraints, credit usage, and related tools. An agent has enough context to invoke it correctly without additional discovery.

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 description coverage is very high, so parameter meanings are already well documented. The description still adds useful semantics by clarifying create/update behavior for flowId and name and by stating that array fields replace stored arrays when passed and remain unchanged when omitted.

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 gives a specific verb and resource: create or update a Flow Studio flow. It clearly distinguishes creation via no flowId and required name from updating an existing flow via flowId, and it states the return shape { flowId, version }.

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?

It explicitly covers when to create versus update, notes that updating a non-owned/missing flow returns 404, and points to run_flow for execution. It also explains that a flow with characters and seasons serves as a series for episode tools, giving clear downstream context.

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

All Galatic.ai tools Inspect

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.