Skip to main content
Glama

ai_modeling_dcc_status

Read-only

Check a local DCC Bridge handshake for a chosen target (Blender, Unity, Unreal, Maya, and others) before importing any file, so you can confirm the connection is ready.

Instructions

check the selected local DCC Bridge handshake without importing a file

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

Input Schema

NameRequiredDescriptionDefault
portNoOptional loopback plugin port; default follows the Studio DCC preset.
targetYes
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value by clarifying it does not import a file, i.e. it is a non-mutating probe. It still omits what the check actually reports, what happens on timeout, or whether a failed handshake is an error or a false result.

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 filler, and the most important qualifier ('without importing a file') comes last but is still short. Brevity is efficient rather than padded, though it tips toward under-specification.

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?

For a three-parameter diagnostic tool with no output schema and sparse schema descriptions, the definition leaves key gaps: what a handshake result contains, how to act on failure, and the role of the port and timeout parameters. The one-liner is not enough for an agent to call and interpret it confidently.

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 33% – just 'port' is documented. The description does not compensate: 'selected' target is unexplained (how the target relates to the enumerated app list), and timeout_seconds (default 60, max 600) is never mentioned even though its semantics matter for a connectivity probe.

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?

Names a specific verb ('check') and resource ('local DCC Bridge handshake') and scopes it with 'selected' and 'local', which separates it from send/targets-style siblings. The 'without importing a file' clause reinforces that this is a probe, not an import action, though the noun 'handshake' is jargon an agent may have to infer.

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: a pre-flight connectivity check before sending or importing. No explicit when/when-not statement, no prerequisites (does a DCC app need to be open?), and no named alternative such as ai_modeling_dcc_targets for discovery.

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