Skip to main content
Glama

splat_engine_status

Reports the configured splat engine, checks whether required CLI tools are present, and returns verification status to diagnose missing dependencies before 3D generation.

Instructions

Report which splat engine is configured and whether the real CLI tools are actually present (requires uv sync --extra engine).

Return Format

{"success": True, "engine": str, "configured": bool, "max_iterations": int, "note": str, "message": str, "verified": "pending"|"ok"|"broken"|"missing", "engine_version": str, "engine_error": str} — message mirrors note so fleet tooling can render the result without special-casing it. configured is the fast exe check; verified is the cached ns-train --help truth (pending until the background probe lands).

Examples

splat_engine_status() -> {"success": True, "engine": "nerfstudio", "configured": True, "max_iterations": 15000, "note": ..., "message": ...}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "splat_engine_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden well: it distinguishes the fast exe check (`configured`) from the cached `ns-train --help` probe (`verified`), enumerates the pending/ok/broken/missing states, and explains the background probe latency. It stops short of stating that the tool is strictly read-only and side-effect free.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is front-loaded and useful, but the large Return Format block largely duplicates a field-by-field output schema that is already present. Only the `message`/`note` mirroring and the `configured` vs `verified` distinction add real value; the rest is restatement.

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 zero-argument diagnostic with an existing output schema, the description supplies the interpretive context an agent needs (what 'configured' means versus 'verified', and why 'verified' may read 'pending'). The prerequisite note about installing the engine extra rounds it out.

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

Parameters4/5

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

Zero parameters, so the baseline is 4. The example call `splat_engine_status()` reinforces that no arguments are accepted, consistent with `additionalProperties: false`.

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 ('Report') and a precise resource: which splat engine is configured and whether the real CLI tools are present. It is clearly a diagnostic/read tool distinct from splat_generate or server_shutdown, though it never names those siblings explicitly.

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?

Usage is implied by the diagnostic framing and the parenthetical prerequisite (`uv sync --extra engine`), but there is no explicit when-to-call guidance, no statement of when to prefer this over show_status_card, and no note on whether repeated calls are cheap.

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