Skip to main content
Glama

import_external_asset

Downloads asset metadata and URLs, then imports the asset into Blender once a local path is available. Use it to bring external assets by source, ID, type, and resolution.

Instructions

Download metadata/URLs then ask Blender to import when a local path is available.

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": {
      "source": "<source>",
      "asset_id": "<asset_id>"
    },
    "name": "import_external_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
asset_idYes
asset_typeNo
resolutionNo1k

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It implies a network download plus a scene mutation but never states permission/credential requirements, what happens when no local path is available (the failure mode the sentence itself raises), or whether the import modifies the current scene.

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 sentence with no padding, so it is concise. However, brevity here comes at the cost of substance, and the ordering of the implied workflow (download first, import second) is the only structural signal provided.

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?

An output schema exists, so return values need not be described, but the rest is thin for a four-parameter, zero-annotation tool: no parameter meaning, no precondition detail, and no differentiation from sibling import tools. An agent could not call this confidently from the definition alone.

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% across four parameters (source, asset_id, asset_type, resolution), so the description was expected to compensate. It explains none of them: 'source' and 'asset_id' are never described, 'resolution' (default '1k') is unmentioned, and the word 'path' in the description does not map to any declared parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names an action sequence (download metadata/URLs, then have Blender import) and implies an external-asset scope, so the general intent is inferable. But 'Download metadata/URLs then ask Blender to import when a local path is available' is murky about what is actually produced or added to the scene, and it gives no signal distinguishing it from siblings like import_asset or import_polyhaven_via_blender.

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. The phrase 'when a local path is available' hints at a precondition, but it is never stated as a rule and no alternative tool is named, even though import_asset and import_polyhaven_via_blender exist as plausible choices.

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