Skip to main content
Glama

Table read track

table_read
Read-only

The ordered dialogue track of the production: every spoken line in scene order with its character, word count and estimated spoken duration, plus a voice-casting sheet per character (speeches, words, estimated time, suggested voice slot) — the casting and read-through preparation a director's team works from. Use it to prepare a table read, plan voice casting or estimate how long the dialogue runs. Data only; no audio is generated.

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": {
      "project_id": "<project_id>"
    },
    "name": "table_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description's genuinely additive note is "Data only; no audio is generated," which prevents an agent from expecting an audio asset from a 'table read' tool; beyond that it says nothing about cost, latency or whether results are cached/computed on demand.

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 what, followed by the when-to-use and a closing scope caveat; nothing is redundant. The opening clause is dense and em-dash-heavy, but every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shape need not be re-explained, and the description correctly focuses on content and purpose. With only one parameter and full annotation coverage, the definition is essentially complete; the only omission is any statement about project_id.

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

Parameters3/5

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

The single required parameter, project_id, is never mentioned in the description, and schema coverage is 0%. Mitigating factor: a lone required id named project_id in a project-scoped toolset is close to self-documenting, so this is a mild rather than fatal gap.

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 names a specific artifact (the ordered dialogue track with per-line character, word count and duration, plus a per-character voice-casting sheet) and frames it as read-through preparation. That is concrete enough to separate it from the schedule/budget/breakdown siblings without needing to name them.

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?

"Use it to prepare a table read, plan voice casting or estimate how long the dialogue runs" gives clear positive triggers. It stops short of exclusions — it does not say when to prefer get_breakdown for character data or that this is unnecessary if only scene timing is needed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources