OpenKatana · Inspect model3d:
OpenKatana_inspect_model3d provides access to OpenKatana’s 3D model inspection tool, helping you check a model asset before using it in a scene. The supplied scene-validation code also calls model inspection when checking objects of type model, showing that inspection is part of OpenKatana’s model-checking process. This makes the node useful as a preliminary checkpoint when preparing external assets for a 3D workflow. It operates through OpenKatana’s tool-calling system rather than generating a new model. The supplied code does not include the inspection implementation, so supported file formats, the exact checks performed, and the availability of details such as geometry statistics, materials, or animation information cannot be confirmed.
OpenKatana · Inspect model3d Input Parameters:
project_id
A required STRING passed to OpenKatana’s argument-building helper together with the tool name and the supplied arguments. It provides the project identifier used when preparing the inspection request, so you should use the identifier associated with your intended OpenKatana workflow. The supplied code does not establish whether inspection requires an existing project or how this identifier affects file-path resolution. No default value, minimum or maximum length, or list of permitted values is shown.
arguments
A required STRING used to supply the inspection tool’s arguments. The node processes this text through its argument-building helpers before calling the tool; it is not a separate model-file input socket. The underlying inspection function shown in the context accepts a source argument, indicating that the inspection implementation needs a model source, but the complete tool signature and the text parser are not included. If the installed tool confirms that it accepts a JSON object containing source, an example would be {"source":"/path/to/model.glb"}; this illustrates argument structure only and does not confirm GLB support. Check the node’s installed description, which is constructed to include the tool signature, for the accepted fields. No default value, size limit, or predefined options are shown.
after
An optional STRING accepted by the execution method, with a Python default of None when omitted. In the supplied method, this value is not referenced when building the tool arguments or invoking the inspection tool, so it has no demonstrated effect on the inspection request itself. Its role elsewhere in OpenKatana’s workflow infrastructure is not shown; do not assume that entering text here imports a model, changes the inspection settings, or passes information to the inspector. No string default, length limits, or permitted options are provided.
OpenKatana · Inspect model3d Output Parameters:
result_json
A STRING containing the response produced by OpenKatana’s response-handling helper after the inspection tool is invoked. This is the node’s only output, so it is where you should look for the returned inspection information or any diagnostic information included in the response. It is a textual result rather than a model asset, image, or rendered preview. Although the output name identifies it as JSON, the response helper and inspection return structure are not supplied, so exact field names, report contents, and error-response structure cannot be documented reliably. Examine an actual successful response before configuring downstream steps that depend on particular fields.
OpenKatana · Inspect model3d Usage Tips:
- Check the installed node description before preparing
arguments. The wrapper builds that description from the tool description and signature, making it the appropriate place to verify the inspection tool’s accepted argument names. - Start with one known, accessible model asset and a minimal request. The supplied inspection function accepts
source, but confirm the exposed tool’s argument structure before using the example JSON. - Use a source location accessible from the machine running OpenKatana. A path on your own computer may not be available when ComfyUI runs on a remote server or inside a container; an absolute path can help remove ambiguity when filesystem paths are supported.
- Keep
project_idconsistent with the project you intend to work in. Do not assume that relative model paths are resolved against that project, because the supplied code does not show the path-resolution rules. - Connect
result_jsonto a text-display or logging step and inspect the actual response before building automated decisions around it. Avoid assuming that it contains polygon counts, texture lists, animation names, or other specific fields. - Treat inspection as a checking step, not as a replacement for importing or rendering. The context shows a separate
import_model3dtool, and the supplied inspection code does not demonstrate asset copying, model repair, conversion, or preview generation. - Leave
afterunconnected unless your surrounding workflow requires it. The execution method shown does not use its value to configure inspection, and no quality, speed, or detail-level controls are exposed by this node interface.
OpenKatana · Inspect model3d Common Errors and Solutions:
unexpected inputs: ...
- Explanation: This is the explicit error-message pattern in the supplied wrapper. It raises a
TypeErrorwhen extra execution fields are provided that are not declared in the tool’s typed required or optional inputs. - Solution: Use only the exposed sockets:
project_id,arguments, and optionallyafter. Put tool-specific information insideargumentsin the supported format rather than adding custom sockets or execution fields.
Missing required input: project_id or arguments
- Explanation: This is a diagnostic description, not a verified error string. Both inputs are required by the authoritative interface, and the execution method has no defaults for them. Omitting either can prevent execution before inspection begins.
- Solution: Supply both required inputs. Use the intended project identifier and provide the tool arguments in the format documented by the installed tool signature.
Arguments could not be parsed or accepted
- Explanation: The exact error text is not supplied. The node processes
argumentsthrough argument-building helpers, so incorrectly formatted text or fields that do not match the tool’s contract may prevent a valid inspection call. - Solution: Verify the accepted format and field names in the installed node description. If JSON is required, use double quotes around property names and string values, remove trailing commas, and avoid including explanatory text around the object.
Model source is missing or cannot be accessed
- Explanation: This is a possible troubleshooting condition, not a quoted implementation error. The supplied inspection function requires a
sourceargument; inspection cannot examine the intended asset if the source is absent, points to the wrong location, or is inaccessible to the running process. - Solution: Confirm how the exposed tool expects the source to be supplied, check that the file exists in the runtime environment, and verify read permissions. If using a remote or container-based installation, make the asset available there rather than supplying a path that exists only on your desktop.
Model inspection fails for the selected file
- Explanation: The inspection implementation and its error messages are not included, so specific format or file-validation failures cannot be enumerated. A failed inspection does not by itself establish whether the problem is an unsupported format, damaged asset, or another implementation requirement.
- Solution: Read the returned diagnostic information or execution log before changing the asset. Verify supported formats against the installed inspection tool, test with a known-working model, and check that the selected file opens correctly in the application that created or exported it.
result_json does not contain the expected report field
- Explanation: The supplied context does not define the inspection response schema. A downstream step expecting a particular field may fail even when the tool returns a response, especially if that field was assumed rather than verified.
- Solution: Display the complete
result_jsonvalue first, check whether it represents a successful inspection or a diagnostic response, and configure downstream parsing to match the actual structure. Do not assume that this output contains a model file or rendered preview.
