Galatic.ai

Save episode

save_episode

Create an episode (no episodeId) or update one. season: 1-99, or 0 for Extras; chapter: {number, title} or null. seriesId is the flowId of the Flow Studio flow that holds the series (from list_flows).

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

Input Schema

Name	Required	Description
`order`	No
`title`	No
`scenes`	No
`season`	No
`chapter`	No
`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."
`seriesId`	Yes
`episodeId`	No
`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.
`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.

First observedOct 24, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=false, so the safety surface is largely covered. The description adds the create/update branching but says nothing about whether an update replaces or merges existing fields, what happens to omitted fields, or any auth prerequisites. For a non-idempotent mutation tool that silence is a real gap.

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?

Three compact clauses with zero padding, and the primary action is front-loaded before the parameter details. Nothing repeats the schema or annotations verbatim.

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 10-parameter mutation tool with 30% schema coverage and no output schema, the description covers the tricky parameters but omits scenes entirely, which is the substantive payload of an episode. The absence of any merge-vs-replace semantics on update also leaves an agent unsure what an update call does to existing content.

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 only 30%, and the description compensates by documenting constraints the schema does not: season is 1-99 with 0 meaning Extras, chapter is {number, title} or null (the schema types chapter as an empty object, so this is essential), and seriesId is a Flow Studio flowId. It leaves order, title and scenes undefined, so coverage is incomplete but it does meaningful work.

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 plus the create-vs-update split inline: "Create an episode (no episodeId) or update one." An agent can distinguish it from read-side siblings like get_episode and list_episodes. It stops short of naming adjacent write siblings such as generate_episode or draft_episode_script, so sibling differentiation is only partial.

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?

The create/update condition is explicit and actionable (omit episodeId to create). It also routes the agent to list_flows as the source of seriesId, which is real cross-tool guidance. It does not cover when to prefer this over generate_episode or publish_episode, leaving the main workflow choice to inference.

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.