Skip to main content
Glama

ai_modeling_dcc_targets

Read-only

List available Studio DCC Bridge targets, loopback ports, and recommended export settings so agents can configure exports and connect to compatible DCC applications.

Instructions

list Studio DCC Bridge targets, loopback ports and recommended export settings

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ai_modeling_dcc_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds useful behavioral context by naming what the call surfaces (targets, loopback ports, recommended export settings), but it omits whether the local bridge must be active, what happens when no bridge is found, and whether the openWorld call can block or time out.

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 clause with no filler; the most important element (the resource being listed) comes first and the payload details follow. It is a noun-phrase label rather than a sentence, which is terse but not padded.

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 zero-parameter, read-only discovery tool with no output schema, the description is adequate but thin: it tells the agent what categories of data come back but not the shape, cardinality, or what 'recommended export settings' concretely contain. Given the absence of an output schema, a sentence on the return structure or the bridge-availability requirement would have closed the gap.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description correctly implies a parameterless enumeration rather than suggesting any filtering or selection arguments.

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 (list) and resource (Studio DCC Bridge targets), and adds the payload contents (loopback ports, recommended export settings), which makes it more than a restatement of the tool name. It does not, however, distinguish itself from the similarly named sibling ai_modeling_print_targets, so an agent must infer that one is a printer/print-related target listing and the other is the DCC bridge target listing.

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: an agent can infer this is the discovery step before ai_modeling_dcc_send or ai_modeling_dcc_status, but the description never says so, never states prerequisites (e.g. whether the Studio DCC Bridge must be running locally), and never excludes alternatives such as print_targets. No explicit when-to-use or when-not-to-use guidance is present.

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