Skip to main content
Glama

inspect_project

Read-only

List bins and project items—including media, sequences, and graphics—with IDs, types, and durations to inspect a FilmCraft project or connected app.

Instructions

List bins and project items (media, sequences, graphics) with ids, types and durations.

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

Input Schema

NameRequiredDescriptionDefault
projectNoPath to the .fcproj project file; omit to edit the FilmCraft app connected with connect_app

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 declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds what comes back (ids, types, durations), which is useful, but says nothing about result size, hierarchy of bins, or behavior when no project is connected — the description does not contradict the annotations.

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 verb and resource, with the returned attributes appended. No filler, no redundant restatement of the tool name.

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 read-only tool with no output schema, the description covers what is enumerated and which fields are returned. Slightly incomplete in that it does not explain bin/item hierarchy or how to distinguish the returned sequences from timeline clips.

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 description coverage is 100% and the single optional 'project' parameter is fully documented in the schema, including the omit-to-use-connected-app behavior. The description adds no meaning beyond that, so the baseline of 3 applies.

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 ('List') plus the resource ('bins and project items') and enumerates the item kinds (media, sequences, graphics) along with returned fields. That scope implicitly separates it from list_timeline, though it never names that sibling or the app-vs-file targeting.

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 only implied: an agent can infer this is the discovery tool for project structure before acting on clips. There is no explicit when-to-use, no statement of when to prefer list_timeline or probe_media, and no mention of the connect_app alternative when the project path is omitted.

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