Skip to main content
Glama

sand3d_format_guide

Read-onlyIdempotent

Explains Sand3D GLB conventions—meters, Y-up, root scale, part names, materials and joint storage in extras—so you can load downloaded models correctly. Read it before writing loader code.

Instructions

How Sand3D GLB files are built (meters, Y up, root scale 0.001, part names, materials), how joints are stored in extras.s3d_joint and how to move them in three.js, the program format, licenses and fair use. Read before writing code that loads a downloaded model.

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": "sand3d_format_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation, so the description does not need to repeat safety details. It adds useful scope by listing the topics the guide covers, but it does not say how the guide is returned, whether it includes code examples, or how long it is.

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?

The definition is compact and front-loads the format topics before the imperative reading instruction. The topic list is dense but purposeful, and no sentence is wasted. A bulleted structure might improve scanability, but the current form is efficient.

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

Completeness5/5

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

For a zero-parameter reference tool with no output schema and read-only annotations, the description supplies enough context: what the guide covers and when an agent should read it. Nothing needed to decide whether to invoke it is missing. Additional return-format details would be nice but are not essential here.

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?

The tool takes zero parameters, so there are no parameter semantics for the description to clarify. The baseline for a parameterless tool is 4, and nothing in the description creates confusion about inputs.

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?

The description clearly identifies this as a format guide for Sand3D GLB files and enumerates the specific topics covered: units, axes, root scale, part naming, materials, joint storage, three.js movement, program format, licenses, and fair use. It is distinguishable from the sibling data-retrieval tools, though it does not explicitly state that it returns documentation content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit usage condition: read it before writing code that loads a downloaded model. That is clear and actionable. It does not discuss when not to use it or name alternatives, but the sibling tools serve different purposes and are unlikely to be confused with a format guide.

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