Skip to main content
Glama
Sign In
splatcraft

splatcraft

Official
by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Splat Info

splat_info

Inspect a 3D Gaussian Splat file (.ply or .spz) and return its metadata to validate inputs and guide conversion, compression, or training workflows.

Instructions

Inspects a 3D Gaussian Splat file (.ply, .spz) and returns its metadata.

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>"
    },
    "name": "splat_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to the splat file.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; 'Inspects' and 'returns its metadata' do imply a non-destructive read, which is meaningful context. However, it says nothing about failure modes (missing/unsupported file, corrupt header), whether the whole file is loaded into memory, or any size limits. The existence of an output schema relieves it of describing return values, keeping this at an adequate 3.

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?

One front-loaded sentence with no filler; the formats are parenthetically embedded efficiently. It is perhaps too terse for a tool with zero annotation coverage, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with a published output schema, the definition covers what it does, what input it accepts, and what it returns. The only shortfall is the absence of any error/edge-case context, which is a minor gap given the low complexity.

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 coverage is 100% and the single parameter is already documented as 'Path to the splat file.' The description only adds the accepted extensions (.ply, .spz), which is a small but genuine constraint beyond the schema; baseline 3 applies since the schema does the heavy lifting.

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 and resource ('Inspects a 3D Gaussian Splat file') and even names the accepted file formats (.ply, .spz), which clearly separates it from siblings like splat_convert or splat_train_local. It does not explicitly contrast itself with splat_probe_local_engines, but the 'returns its metadata' clause makes the read-only inspection role unambiguous.

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, and no alternative is named. An agent must infer from the word 'metadata' that this is a pre-flight/inspection step before converting or training, but that inference is never 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