Skip to main content
Glama
abrahamADSK

fpt-mcp

by abrahamADSK
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

fpt_launch_app

Launch a DCC application scoped to a ShotGrid entity, using Toolkit for context injection or falling back to direct open. Supports Maya, Flame, and others.

Instructions

Launch a DCC application scoped to a ShotGrid entity.

Discovery is OS-first: if the app is not installed on this machine the tool fails immediately without consulting ShotGrid. When the owning project has an Advanced Setup PipelineConfiguration whose tank CLI is reachable on disk, the launch is routed through tank so Toolkit pre-launch hooks run and the app opens in the correct context. Otherwise the tool falls back to a direct open -a launch and surfaces a warning — the app still opens, but without context injection from Toolkit.

Version selection: the FPT-selected version (SG Software version_names) is authoritative over "newest installed"; a warning names both when the selected one is not installed locally.

MAYA / Sequence: a bare Sequence launch is step-LESS (no work templates); the tank route resolves it to its Step Task (step param, default Layout) so Maya boots the sequence_layout env.

FLAME (route='auto'/'direct'): composes startApplication --start-project=<name> ... --closed-libs — SG name slugified via tk-flame's convention and validated against the local Stone+Wire project list; no Toolkit/SSO needed. Refusals to relay: "does not exist on this workstation" (direct route cannot create projects — offer route='toolkit', which pre-creates via Wiretap) and "already running" (single-instance + project locks; close it or force=true).

Common failure modes to explain to the user if they surface:

  • error: "... is not installed ..." — the DCC binary is not under the expected install path. Tell the user to install it and retry.

  • Popen succeeds but the launched process dies immediately with a tank message like EOF when reading a line or Authentication ... expired. This means the Toolkit tank CLI lost its cached session. The user must run <PipelineConfiguration>/tank <Entity> <id> once in an interactive terminal, authenticate via the browser, and retry. The tool cannot do this because it cannot deliver the browser approval step.

  • Popen succeeds but tank errors with does not exist on disk for an engine (e.g. tk-shell v0.10.2). The pipeline config expects bundles under <config>/install/ which are absent. Suggest the user add bundle_cache_fallback_roots pointing to ~/Library/Caches/Shotgun/bundle_cache in the config's pipeline_configuration.yml.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Without annotations, the description must disclose all behavioral traits. It does so comprehensively: OS-first discovery, fallback behavior, version selection, warning generation, specific handling for Maya and Flame, and detailed failure modes including authentication issues and missing engine bundles.

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 description is lengthy but well-structured with clear sections for core behavior, per-DCC details, and failure modes. It is front-loaded with the essential purpose. While every sentence adds value, the length could be slightly reduced for extreme conciseness, but given the complexity, it remains effective.

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?

Given the tool's complexity, number of parameters, and absence of annotations, the description is exceptionally complete. It covers all behavioral aspects, platform-specific nuances, error handling, and contextual details, leaving no significant gaps for an AI agent to understand correct invocation.

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

Parameters5/5

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

The description adds significant meaning beyond the input schema. It explains the step parameter for Sequence launches, the force parameter's single-instance guards, and the route parameter's behavior for different DCCs, providing context that the schema alone does not convey.

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 clearly states the tool's purpose: launching a DCC application scoped to a ShotGrid entity. It specifies supported apps (Maya, Flame) and provides distinct behavior, effectively differentiating it from sibling tools like fpt_bulk or sg_create.

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

Usage Guidelines5/5

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

The description provides extensive usage guidelines, including when to use different routes (auto, direct, toolkit), handling of various DCCs, and detailed common failure modes with recommendations. It implicitly guides the agent on selecting this tool for context-specific launches.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/abrahamADSK/fpt-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server