Skip to main content
Glama

save_project

Persist the open video project to its current file or a specified .fcproj path, so edits are stored for handoff or later editing.

Instructions

Save the project open in the connected app (to its own file, or to path).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoSave As this .fcproj instead

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish this is a non-read-only, non-open-world mutation. The description adds useful context that it acts on the currently open project in the connected app and that `path` switches to Save As semantics. It stops short of stating overwrite behavior for an existing target file, what happens if no app is connected, or whether the save is synchronous.

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?

One sentence, front-loaded with the core action, with the two save modes packed into a parenthetical. Nothing is padded and nothing essential is buried.

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?

For a one-optional-parameter mutation with annotations present and no output schema, the description covers the essential question of what gets written and where. The remaining gaps (connected-app prerequisite, overwrite behavior on an existing path) are small but non-zero for a write operation.

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?

Schema coverage is 100% and the single optional parameter is already documented as "Save As this .fcproj instead." The description restates that mapping and clarifies the no-argument default (save to its own file), which is a modest addition rather than new syntax or constraint detail. Baseline 3 applies when the schema carries the parameter documentation.

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?

The description gives a specific verb (Save) and resource (the project open in the connected app), and its parenthetical distinguishes two scopes: saving to the project's own file versus a supplied path. It does not name a sibling, but the boundary against create_project and inspect_project is self-evident from the verb.

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?

Usage is implied: call this to persist the current project, and pass `path` for a Save As. There is no explicit when-to-use versus when-not, and no mention that the app must be connected first (connect_app/app_status are siblings), which is a real prerequisite an agent must infer.

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