Skip to main content
Glama
Sign In
splatcraft

splatcraft

Official
by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Splat Create World

splat_create_world

Generate a 3D radiance field world from a text prompt using the World Labs Marble API; optionally name scenes or run a credit-free dry run.

Instructions

Generates a 3D radiance field world via World Labs Marble API.

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": {
      "prompt": "<prompt>"
    },
    "name": "splat_create_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional scene name.
modelNoWorld Labs model tier (default: marble-1.1).marble-1.1
promptYesNatural language description of the world.
dry_runNoSimulate generation without consuming API credits.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 one sentence cannot cover it. It does not disclose that this is a paid, likely long-running remote generation call, whether it is synchronous or job-based, or that partial failures may still consume credits — the only hint of cost is buried in the dry_run parameter description.

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 or redundancy. It is efficient, though its terseness leaves nothing to structure and gives no secondary cues about cost or latency.

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?

The tool is a generative, credit-consuming operation with no annotations, and the description says nothing about cost, duration, or failure modes. An output schema exists so return values need not be explained, but the operational picture is still too thin for a tool of this weight.

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters including defaults and the credit-saving dry_run flag are already documented in the schema. The description adds no meaning beyond it, which is the baseline case when the schema does the work.

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?

States a specific verb ('Generates') and a specific resource ('3D radiance field world') plus the underlying provider (World Labs Marble API), which distinguishes it from siblings like splat_convert or splat_collider. It stops short of an explicit contrast with splat_train_local, which is the nearest ambiguous neighbor.

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 when-to-use guidance, no mention of alternatives, and no statement of prerequisites such as API credentials or whether a remote service must be reachable. An agent cannot tell from the description whether to call this versus splat_train_local for producing a world.

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