Skip to main content
Glama

Get one production playbook

get_film_playbook
Read-onlyIdempotent

Get one production playbook by id, including primary servers, setup order, auth requirements, workflow steps, failure modes, fallback servers, constraints, and links to each server's mcp.film page. Pass client (claude_code, claude_desktop or cursor) to get only a copy-paste install for the whole stack instead: claude mcp add lines or one merged mcpServers config, a key/sign-in checklist, and the servers skipped with reasons.

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": {
      "id": "<id>"
    },
    "name": "get_film_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPlaybook id, e.g. 'commercial-sprint' or 'local-edit-bay'
clientNoOptional. Return the whole-stack install script for this client instead of the playbook.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / client
      Added value: +{
      +  "description": "Optional. Return the whole-stack install script for this client instead of the playbook.",
      +  "enum": [
      +    "claude_code",
      +    "claude_desktop",
      +    "cursor"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and closed-world, and the description adds substantial context beyond them: exactly what sections the playbook contains (setup order, auth requirements, failure modes, fallback servers, constraints) and what the install-mode response includes (skipped servers with reasons). That is a rich disclosure of return content for a tool with no output schema.

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?

Two sentences, front-loaded with the primary behavior and then the alternate mode; no filler. The long enumeration of returned sections is dense but each item adds information. Slightly heavy for a single sentence but justified by the missing output schema.

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?

No output schema exists, so the description must carry the return-shape burden, and it does so for both the default and client modes. With annotations covering the safety profile and 100% schema coverage on the two params, an agent has everything needed to call it 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 100% with the id example and client enum already documented, so the baseline is 3. The description earns above baseline by explaining the semantic effect of client — it replaces the playbook with a whole-stack install script — which is more than the schema's 'instead of the playbook' phrasing conveys about the resulting content.

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?

States a specific verb and resource ('Get one production playbook by id') and enumerates the returned payload, so an agent can distinguish it from list_film_playbooks. It also covers the second mode. It does not explicitly name the sibling it overlaps with, get_install_config, so it falls short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The client branch has clear conditional guidance ('Pass client ... to get only a copy-paste install for the whole stack instead'), which is genuinely useful. However, there is no guidance on when to pick this tool over get_install_config or plan_film_stack, nor any stated prerequisites. Usage for the default mode is only implied.

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.