Skip to main content
Glama

get_script

Read-onlyIdempotent

Reads a film's script data—title, chosen voice, and lines with IDs, text, feeling, voice status, duration, and speaking shots—to assign, speak, or voice lines.

Instructions

Read-only: the film's script from Sound and script: title, the chosen voice, every line (id, text, feeling, whether it has a voice and how long) and which shots speak it. Use line ids with assign_line, speak or own_voice. To put a script in, use write_script.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_script"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotent, non-destructive, closed-world), so repeating 'Read-only' earns no credit. What the description does add beyond them is substantive: the exact shape of the payload, including that lines carry ids, feelings, voice presence and durations, and that shot-to-line relationships are included. It says nothing about ordering, pagination or size limits, but for a zero-parameter local read that is a minor gap.

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?

Front-loaded with the operation and its scope, followed by a compact field enumeration and two routing sentences; nothing is padding. The opening phrase 'from Sound and script' is awkwardly worded and slightly slows parsing, but the overall density is good.

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?

With no parameters and no output schema, the description must carry the entire return-value burden, and it does by naming each field the agent will receive and the downstream tools the ids feed. There is nothing further an agent needs in order to call this 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?

The tool takes no parameters, so there is no input semantics to document and the baseline applies. The description appropriately spends its words on outputs instead of inventing parameter guidance.

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?

States a specific read operation on a specific resource ('the film's script') and then enumerates what comes back: title, chosen voice, per-line id/text/feeling/voice/duration, and which shots speak each line. It explicitly distinguishes itself from write_script, so an agent can select it without opening any schema.

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?

Gives a clear routing rule for the write direction ('To put a script in, use write_script') and points at the follow-up tools that consume the returned line ids (assign_line, speak, own_voice). It stops short of an explicit 'call this when you need to inspect or edit existing lines' statement, so the read-side trigger is implied rather than stated.

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