Galatic.ai

Get episode

get_episode

Read-onlyIdempotent

Get one episode: its full record (title, status, season, chapter, scenes and script, contentUrl once rendered), with media URLs freshly signed. Use list_episodes to find an episodeId and save_episode to change it; use generate_episode with action "status" to follow a render. Read-only; 404 when the series is not the caller's or the episode does not exist. 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>",
      "episodeId": "<episodeId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "get_episode"
  }
}

Input Schema

Name	Required	Description
`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`	Yes
`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

A4.9/5.0

Behavior5/5

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

The annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, and the description adds meaningful context beyond that: media URLs are freshly signed, contentUrl appears only once rendered, and the tool returns 404 when the caller does not own the series or the episode does not exist. These details help the agent interpret failures and understand what the returned record will contain.

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 front-loaded with what the tool returns, then routes the agent to alternative tools, then states read-only behavior and the 404 condition. Every sentence contributes useful selection or invocation guidance, with no redundant restatement of the schema or annotations.

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?

There is no output schema, but the description enumerates the key fields in the full episode record and notes that media URLs are freshly signed and contentUrl appears once rendered. It also covers ownership-related 404 behavior and the origin of seriesId, which is sufficient for an agent to call and interpret this read-only tool correctly.

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 60%, and the description adds important meaning for seriesId by explaining that it is the flowId of the Flow Studio flow holding the series, sourced from list_flows. It also implies how to obtain episodeId via list_episodes. It does not add meaning for context or conversation_id beyond the schema descriptions, so it falls short of a perfect score.

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 states a specific verb and resource: retrieve one episode and its full record, including title, status, season, chapter, scenes, script, and contentUrl. It also distinguishes the tool from siblings by naming list_episodes for discovery, save_episode for changes, and generate_episode for render status.

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 explicitly identifies when to use list_episodes to find an episodeId, save_episode to modify an episode, and generate_episode with action "status" to follow a render. It also clarifies that seriesId comes from list_flows, which gives the agent the complete lookup path.

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.