3dassets

Get usage snippet

get_asset_usage

Obtain framework-specific code and steps to load any 3D asset in three.js, React Three Fiber, model-viewer, Blender, Godot, or Unity. Select your framework to get the exact integration steps.

Instructions

Code or steps to load an asset in three.js, React Three Fiber, , Blender, Godot or Unity.

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": {
      "slug": "<slug>"
    },
    "name": "get_asset_usage"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes
`framework`	No		threejs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations and a minimal description, the behavior is only implied as returning code or steps. There is no mention of output format, potential side effects, or whether it is a read-only operation.

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

Conciseness5/5

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

The description is a single concise sentence with no unnecessary words. It directly conveys the tool's purpose.

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?

The description covers the core purpose, but lacks details about the expected output structure or any additional context such as error conditions. For a simple retrieval tool, the missing output information is a notable gap.

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?

The schema defines slug and framework but provides no descriptions. The tool description does not explain the meaning or purpose of these parameters, leaving the agent to infer from context. Since schema description coverage is 0%, the description should compensate but does not.

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 clearly states the tool returns code or steps to load an asset in various frameworks, which distinguishes it from asset metadata tools. It is specific about the resource and action, though it doesn't explicitly name the verb 'get'.

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?

No guidance is provided on when to use this tool versus alternatives like get_asset or search_assets. The description does not mention conditions or scenarios where this tool is preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.