Skip to main content
Glama

Shooting schedule

get_schedule
Read-only

The shooting schedule of the production — the stripboard: every shoot day with its scenes, headings, locations, cast and page eighths, in the order the first assistant director will call them. Use it when the user asks how many days the shoot takes, which scenes film on which day, or how the production is boarded.

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

Input Schema

NameRequiredDescriptionDefault
project_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioural context the annotations cannot: the output is ordered as the first AD will call it, and it carries headings, page eighths and cast alongside scenes. It says nothing about permissions, scope of the project read, or pagination for very long shoots.

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?

Two sentences, both earning their place: the first defines the resource and its contents, the second defines the triggering questions. The definitional content is front-loaded before the usage guidance, and there is no filler or repetition of the title.

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 the description is not obliged to spell out return values, and it does not need to. For a single-parameter read tool with full annotation coverage, the only real gap is the absent project_id semantics and any note on sibling differentiation. Everything an agent needs to invoke it correctly is present.

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?

There is a single parameter, project_id, and schema description coverage is 0%, so the schema contributes only the name and type. The description says nothing about it, though 'of the production' implies the identifier selects the production whose stripboard is returned, which is close to self-evident for a single-key lookup. Adequate but no added meaning beyond the obvious.

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?

Names a specific resource (the stripboard/shooting schedule) and enumerates exactly what it contains: shoot days, scenes, headings, locations, cast, page eighths, in 1st-AD call order. This is far more than a restatement of the title. It stops short of explicitly contrasting itself with the neighbouring get_breakdown, so an agent must infer the boundary between a scene breakdown and the boarded schedule.

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 three concrete user-question triggers — shoot duration, which scenes film on which day, and how the production is boarded — which map cleanly onto when to reach for this tool. There is no exclusion guidance telling the agent when to prefer get_breakdown or get_day_out_of_days instead, so the routing for adjacent questions is left to inference.

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