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

mcp-for-cascadeur

by Rickcy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fbx_export_verified

Destructive

Exports a single-character baked FBX after saving a native source copy, verifying model and file integrity, and publishing with destination conflict protection.

Instructions

Save a new native source copy, stage a whole single-character ASCII/Y baked FBX, verify model/file integrity and publish with destination conflict protection.

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>",
      "source_copy_path": "<source_copy_path>"
    },
    "name": "fbx_export_verified"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
end_frameNo
start_frameNo
character_idNo
expected_sha256No
source_copy_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and non-read-only, and the description reinforces this by disclosing that a native source copy is written and that publishing is conflict-protected. However, it does not say what happens on an existing destination beyond 'protection', whether the source copy overwrites anything, or how expected_sha256 failure is handled.

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?

A single sentence that front-loads the pipeline in execution order with no filler. It is dense, though, and jargon such as 'ASCII/Y baked' reduces first-read clarity.

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

Completeness3/5

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

For a destructive, multi-stage export pipeline with no output schema, the description conveys the pipeline stages and conflict protection but leaves parameters, preconditions, and the verification/failure outcome unexplained. It is adequate to know roughly what the tool does, not to call it correctly.

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% for six parameters, so the description must carry the meaning and largely does not: path, source_copy_path, expected_sha256, character_id, start_frame, and end_frame are never explained. 'single-character' and 'baked' only loosely hint at character_id and the frame range.

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 names a concrete multi-step operation (save source copy, stage baked FBX, verify, publish) on a specific resource, and the qualifiers 'whole single-character ASCII/Y baked' scope it beyond a generic export. It does not explicitly name sibling fbx_export or fbx_export_status as alternatives, so differentiation is implied rather than stated.

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?

There is no explicit when-to-use guidance and no mention of the very relevant siblings fbx_export and fbx_export_status, nor of prerequisites (active scene, selected character, existing source copy). An agent must infer that this is the safer/verified path versus plain fbx_export.

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