Skip to main content
Glama

ai_modeling_dcc_send

Send an exported 3D model to a local Studio DCC Bridge and wait for its import receipt, confirming the target application received and loaded the file.

Instructions

send an exported model to a local Studio DCC Bridge and wait for its import receipt

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": {
      "target": "<target>",
      "file_path": "<file_path>"
    },
    "name": "ai_modeling_dcc_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
portNoOptional loopback plugin port; default follows the Studio DCC preset.
targetYes
file_idNoCorrelation ID, not an upstream deduplication guarantee.
file_pathYes
wait_importNoWait for file_loaded; false only confirms transfer.
timeout_secondsNo

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?

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the agent knows this is a non-destructive but externally side-effecting call. The description adds real value by disclosing that the tool blocks waiting for an import receipt — a meaningful behavioral trait — but says nothing about failure modes, what happens on timeout, or whether the transfer is retried or partially applied.

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 front-loaded sentence with no wasted words, naming action, destination, and the wait behavior up front. It is efficient rather than padded, though the same brevity is what leaves the usage gaps above.

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?

A 7-parameter, network-touching tool with no output schema needs more than one clause. The description omits what a 'receipt' contains, how timeout_seconds interacts with wait_import, and what the agent should do if the bridge is unreachable, leaving the definition thin for this complexity.

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 only 43% and the description mentions no parameters at all — not target, not file_path, not the file_id correlation semantics, and not the timeout bound. The schema documents port, file_id, and wait_import, but target and file_path, the two required parameters, are explained nowhere, so the description fails to compensate for the coverage gap.

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 and resource chain — send an exported model to a local Studio DCC Bridge — plus the waiting behavior. It's clearly distinct from dcc_status/dcc_targets in what it does, though it never names the precondition (an already-exported model) or a sibling alternative by name.

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 or when-not-to-use guidance, no stated prerequisites (Studio must be running, a bridge must be listening, the model must already be exported), and no guidance about which target to pick. The invocation context is implied by 'exported model' but nothing in the text routes an agent between this and dcc_status.

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