Skip to main content
Glama
Sign In
splatcraft

splatcraft

Official
by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Splat Collider

splat_collider

Extract oriented bounding boxes and collision meshes from splat files, then write them as GLB or JSON for Gamecraft/Godot.

Instructions

Extracts oriented bounding box and collision mesh (.glb / .json) for gamecraft/Godot.

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": {
      "file_path": "<file_path>",
      "output_path": "<output_path>"
    },
    "name": "splat_collider"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesSource splat file.
output_pathYesPath where collider GLB or JSON should be written.

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?

With no annotations at all, the description bears the full behavioral burden and discloses little beyond the output artifacts. It does not say that it writes a file (overwriting or creating), how the choice between .glb and .json is made, whether the extraction is deterministic, or whether the bounding-box computation has cost/precision considerations.

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 tight sentence with the verb and deliverable front-loaded and zero filler. It is slightly under-specified rather than over-long, leaving the format-selection mechanism unexplained.

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?

An output schema exists, so return values need not be described, and the two-parameter surface is fully documented in the schema. However, for a tool that writes assets to disk and has no annotations, the description leaves the write/overwrite semantics and format selection unaddressed.

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% and only two parameters exist, so the schema already explains both file_path and output_path adequately. The description adds no meaning about valid splat formats for the source or about how the path extension selects GLB versus JSON.

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 ("Extracts") and the concrete artifacts produced ("oriented bounding box and collision mesh") plus output formats (.glb / .json) and target engines. This clearly separates it from siblings like splat_convert or splat_info, though it never names the source artifact as a splat file.

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 when-to-use or when-not-to-use guidance is given relative to splat_convert, splat_info, or splat_create_world. The agent must infer from the output formats that this tool is for producing physics/collision assets, which is implied rather than stated.

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