Skip to main content
Glama

Create call sheet

create_call_sheet
Destructive

Builds the call sheet for one shooting day of the production from its saved schedule — the document the first assistant director issues for the day, from the same data behind the schedule and the Day Out of Days, so nothing is re-typed — and returns a PDF download link plus the sheet itself: the general crew and cast calls, the day's scenes with page counts, the locations and the individual cast calls the second assistant director works from. Fields the plan does not contain (the calendar date, weather, contacts) come back as clearly marked placeholders for the production office to fill, never invented. Call sheets are deliverables of the production: they build once the production is unlocked (Production, US$79 per production, or the Studio slate plan).

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": "create_call_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoThe shooting day to build the call sheet for: a day number from the production's schedule (see get_schedule). Required — without it, the tool answers which days exist instead of building a sheet.
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=false and destructiveHint=true, so the agent knows this is a mutating call; the description adds meaningful behavior it doesn't have to (placeholder fields never invented, PDF link plus sheet content returned, paid-plan gating). However, the destructiveHint=true is never explained — nothing says whether an existing call sheet for that day is overwritten, replaced, or duplicated, which is exactly the risk the annotation signals. That gap keeps it at an adequate-but-incomplete 3.

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?

The purpose is front-loaded in the first clause and the remaining detail — placeholder handling, returned contents, plan requirement — is all decision-relevant. It is one dense paragraph with a long appositive ('the document the first assistant director issues for the day...') that could be trimmed without losing information.

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?

Given an output schema exists, the description needn't enumerate return values, yet its summary of the sheet contents is a useful complement rather than filler. Prerequisites and failure/fallback behavior are covered; the only substantive hole is what happens to a pre-existing sheet, which matters for a tool annotated destructive.

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?

With 50% schema coverage, the description partly compensates: it clarifies that 'day' is a shooting-day number drawn from the production's schedule and reinforces the fallback behavior when it's absent. The 'project_id' parameter is undocumented in both the schema and the description, and the scoping language ('of the production') only weakly implies it.

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 opens with a specific verb and resource ('Builds the call sheet for one shooting day of the production from its saved schedule') and pins down both the input source (the schedule / Day Out of Days) and the output (a PDF link plus the sheet). It distinguishes itself from siblings like get_schedule and get_day_out_of_days by positioning those as the underlying data rather than the deliverable.

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?

It gives real context for when this applies — a call sheet is a per-shooting-day deliverable built from an existing schedule — and states the prerequisite that the production must be unlocked (Production US$79 or the Studio slate plan). It also points to get_schedule for day numbers and warns that omitting 'day' returns the available days instead of a sheet. What's missing is explicit routing against siblings such as create_export for document output.

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