Skip to main content
Glama
Sign In
mcp-for-cascadeur

mcp-for-cascadeur

by Rickcy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fbx_export

Destructive

Export a workspace FBX from Cascadeur when the native license permits, choosing animation, scene, model, or selected objects/joints/frames; verify rig and axes in the receiving app.

Instructions

Export a workspace FBX when the native license permits; verify rig and axes in the receiving app.

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": {
      "path": "<path>"
    },
    "name": "fbx_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
pathYes
overwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety bar is lower. The description adds genuinely new context with the license gating and the need to re-verify rig and axes downstream, but it never explains what makes the call destructive — the `overwrite` flag defaults to false and its consequences are unstated.

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?

One front-loaded sentence with no filler, and the license caveat comes before the post-export advice. It is arguably too terse for its complexity, but on the conciseness axis every clause is doing work.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, license-gated mutation with a six-option mode enum, no output schema, and 0% schema documentation, yet the description explains none of the mode semantics or overwrite behavior. It also omits the natural follow-up path through the fbx_export_status/fbx_export_verified siblings that exist for exactly this purpose.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description carries the full burden and provides nothing: neither `path`, `overwrite`, nor the six-valued `mode` enum (animation/scene/model/selected_objects/selected_joints/selected_frames) is mentioned. An agent cannot tell from the description what any mode actually exports.

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 ("Export a workspace FBX"), which is enough to distinguish it from fbx_import and the list tools. It does not differentiate from the closely related fbx_export_status / fbx_export_verified siblings, leaving the agent to guess which one to call after exporting.

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

Usage Guidelines2/5

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

The only usage condition is "when the native license permits," which is a prerequisite rather than guidance about when to call this versus alternatives. Nothing tells the agent to follow up with fbx_export_status or fbx_export_verified, nor when to prefer fbx_import or the scene/selection tools.

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

Deploy Server

Other Tools