3DAssets.dev

Get a walkable pack demo layout

get_demo

Get one demo: the pack, the spawn point, the walkable bounds, the points of interest, and every placement (public asset slug, position in metres, yaw in degrees) with the CDN URL and bounds of each model placed. Load the models with a plain GLTFLoader and apply the transforms to reproduce the scene.

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_demo"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 7, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The description discloses the returned data in detail and implies a read-only 'Get' operation, but with no annotations it does not state side effects, authentication requirements, or failure behavior. It is transparent about output but not about operational behavior.

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?

The description is a single dense sentence that packs all relevant output fields, but it remains focused and avoids fluff. The length is justified by the amount of specific data returned.

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 output structure is well specified, which is important since there is no output schema. However, the description omits the meaning of the slug parameter and any error or edge-case behavior, leaving some context incomplete.

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

Parameters1/5

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

The only parameter, slug, is not explained in the description; the schema only provides pattern and length constraints. The description adds no semantic meaning about what slug refers to or how it should be supplied.

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

Purpose5/5

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

The description clearly states the tool fetches one demo and enumerates its contents (pack, spawn point, walkable bounds, POIs, placements). This distinguishes it from sibling tools like list_demos, get_pack, and get_asset.

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?

The description explains how to use the result ('Load the models with a plain GLTFLoader and apply the transforms'), but it does not explicitly state when to choose this tool over list_demos or other alternatives. Usage guidance is implied rather than direct.

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

All 3DAssets.dev tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.