MoonRay MCP

by tylerart3d

Overview Schema Source Related Servers Discussions Admin

Python

Local

inspect_materials

Check source materials, textures, and translated MoonRay RDL for a scene or job to diagnose rendering issues.

Instructions

Inspect source materials, textures, and a job's translated MoonRay RDL.

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

Input Schema

Name	Required	Description	Default
`scene`	No
`job_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral disclosure burden. 'Inspect' implies a read-only operation, and mentioning 'translated MoonRay RDL' adds useful context about what is actually being examined. However, it does not describe output behavior, errors, or whether any state changes occur.

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 description is a single focused sentence with no filler, and it front-loads the action verb. It is concise and readable, though it sacrifices useful detail for brevity.

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

Completeness2/5

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

The description gives a clear high-level purpose but is incomplete for a tool with no output schema, no parameter descriptions, and no annotations. The agent does not learn what the tool returns, how optional parameters behave, or whether scene and job_id are mutually exclusive or combinable.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for the undocumented scene and job_id parameters. It only hints that a 'job' is involved via 'a job's translated MoonRay RDL' and never explains how scene maps to the described resources. The mapping is left mostly to inference.

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 uses a specific verb ('Inspect') and names concrete resources: source materials, textures, and a job's translated MoonRay RDL. This distinguishes it from siblings like inspect_scene and validate_scene, though the differentiation is implicit rather than explicit.

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 guidance is given about when to use this tool versus siblings such as inspect_scene or validate_scene. There are no exclusions, prerequisites, or alternative routing hints, so the agent must infer usage entirely from the tool name and minimal description.

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