Skip to main content
Glama
Sign In
splatcraft

splatcraft

Official
by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Splat Convert

splat_convert

Convert PLY Gaussian splat files to compressed SPZ format to reduce file size, using source .ply and destination .spz paths.

Instructions

Converts a PLY Gaussian splat file into an SPZ compressed format.

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": {
      "in_path": "<in_path>",
      "out_path": "<out_path>"
    },
    "name": "splat_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
in_pathYesSource .ply file.
out_pathYesDestination .spz file.
target_formatNoTarget format (default: spz).spz

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and says nothing about whether an existing out_path is overwritten, whether the SPZ compression is lossy or how large a fidelity hit to expect, whether the operation is local or remote, or whether it is slow for large splats. Only the input/output formats are disclosed, which the schema already implies.

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?

A single front-loaded sentence with zero filler. Nothing in it is redundant, and it puts the direction of conversion first so the agent reads the essential fact immediately.

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 explained, and the schema documents all three parameters. However, for a file-writing conversion tool with no annotations, the description omits overwrite behavior, expected input validation, and any hints about performance or failure modes, leaving meaningful gaps.

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 the baseline of 3 applies. The description adds no meaning beyond the schema and does not explain the optional target_format parameter or which values beyond the default 'spz' are accepted.

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 (converts) plus both the source and destination formats (PLY Gaussian splat -> SPZ), which is unambiguous. It does not name or contrast any sibling, but the conversion operation is distinct enough that an agent can tell it apart from splat_info or splat_create_world from the description alone.

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 statement of when to reach for this tool instead of splat_info or splat_train_local, and no prerequisites such as the source file needing to exist locally or the output being overwritten. The agent must infer the use case entirely from the name and verb.

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