Skip to main content
Glama

ai_modeling_frontend_export

Export exact Studio GLB or verified static binary FBX to GLB with the webpage engine and persistent lightweight authorization, reusing a request ID to recover results without new authorization.

Instructions

export an exact Studio GLB or verified static binary FBX to GLB with the webpage engine and persistent lightweight authorization

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": {
      "project_id": "<project_id>",
      "operator_id": "<operator_id>",
      "request_id": "<request_id>",
      "destination_path": "<destination_path>",
      "forward_axis": "<forward_axis>",
      "pivot_to_center_bottom": "<pivot_to_center_bottom>"
    },
    "name": "ai_modeling_frontend_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFilename passed to the converter; defaults to the frozen source project name.
formatNoglb
project_idYes
request_idYesPersistent export intent. Reuse it to recover the original result without a new authorization.
max_creditsNoMaximum estimated credits for the persistent export-lite authorization.
operator_idYesExact successful source operator; verified GLB or bounded static binary FBX. GLB supports webpage PBR factors and bounded static root/child TRS or scene deletion with per-file proof.
runtime_dirNoOptional directory containing the exact hash-pinned official JS/WASM runtime; engine files are not bundled.
forward_axisYesExplicit webpage forward axis. Binary FBX currently requires -y.
destination_pathYesCaller-selected GLB path; never overwrites. A retry may use another destination.
exclude_retargetNoExplicitly select no separate retarget motions. Source skeletons and embedded clips are retained; omitted or false keeps the separate-motion guard.
pivot_to_center_bottomYesExplicit webpage bottom-center pivot switch. Binary FBX currently requires true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the agent knows this mutating export tool behaves like an open-world operation whose output is not destructive. The description adds the useful facts that the operation consumes 'persistent lightweight authorization' and depends on an external webpage engine runtime, and it implies credits are involved. It does not explain what the authorization costs, what happens on failure, or that request_id reuse recovers a prior result without new authorization. That last detail appears only in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, but it is dense with undefined jargon such as 'exact Studio GLB', 'webpage engine', and 'persistent lightweight authorization'. It is compact mostly because it omits information callers need, not because it is efficiently phrased.

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 an 11-parameter, 6-required tool that performs a paid, authorization-gated format conversion and writes a file. There is no output schema. Yet the description never covers the authorization and credit flow, retry and idempotency behavior, output artifact location, or how it differs from the multiple sibling export tools. It is far too thin for the complexity of the 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 description coverage is 82%, so the schema already documents most parameters, including request_id persistence, max_credits, destination_path never-overwrites behavior, runtime_dir, and the FBX axis constraints. The description adds no syntax or meaning beyond what the schema says. A 3 is the correct baseline when the schema does the heavy lifting.

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 specific verb (export) and specific resources (an exact Studio GLB, or a verified static binary FBX converted to GLB), and it says the conversion runs through the webpage engine. This is clearer than a name restatement. It does not, however, differentiate this tool from near siblings such as ai_modeling_export_lite, ai_modeling_model_export, or ai_modeling_export_batch, so an agent still cannot tell which export variant to pick from the text alone.

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 description contains no when-to-use, when-not-to-use, or alternative-selection guidance. It does not explain when the persistent authorization flow is appropriate versus a lighter export sibling, and it does not state prerequisites beyond the vague phrase 'verified static binary FBX'. Some constraints exist, such as FBX requiring forward_axis -y and pivot_to_center_bottom true, but those sit in the schema descriptions rather than in the tool description.

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