godot-omni

Overview Schema Source Related Servers Discussions Admin

occluder_manage

Scaffold 3D occluder nodes and 2D light occluder polygons, then inspect occluder resources to manage occlusion culling in Godot scenes.

Instructions

Occlusion Culling Management.

Ops:

scaffold_occluder_3d(parent_path="", occluder_type="box", size=[1.0,1.0,1.0], node_name="OccluderInstance3D") Scaffold a 3D occlusion culling node (box, sphere, quad).
scaffold_occluder_2d(parent_path="", polygon_points=[[-16,-16],[16,-16],[16,16],[-16,16]], closed=True, node_name="LightOccluder2D") Scaffold a 2D light/occlusion polygon node in current scene.
get_occluder_info(occluder_path) Inspect occluder node and attached occluder resource.

Canonical call shape: {"op": "<verb>", "params": {...}}. Flat op parameters are accepted as a compatibility alias when the client transmits them; op and session_id remain top-level.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`op`	Yes
`params`	No
`session_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv5.0.28Sep 23, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are present, so the description carries the behavioral disclosure burden. It distinguishes mutating scaffold operations from the read-only get_occluder_info and notes that the 2D scaffold creates a node 'in current scene'. However, it does not disclose side effects such as scene modification, prerequisites like needing an open scene, or reversibility.

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

Conciseness5/5

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

The description is compact and well-structured: a one-line domain summary, a bulleted operation list, and a call-shape note. Every sentence provides useful information, and the canonical call shape is front-loaded for interoperability.

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

Completeness3/5

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

With an output schema present and the canonical call shape explicitly documented, the description covers most operational needs. However, it leaves minor gaps around scene prerequisites, side effects of scaffolding, and explicit usage alternatives, making it slightly incomplete for an agent without prior context.

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 input schema has 0% description coverage, but the description compensates by listing every operation's parameters with defaults and type hints, such as occluder_type='box' and polygon_points. This gives agents enough information to construct valid params, though it could add more prose per parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the domain (occlusion culling management) and enumerates three distinct operations with specific verbs and resources: scaffold_occluder_3d, scaffold_occluder_2d, and get_occluder_info. This makes the tool's purpose unambiguous and distinguishes it from the broader set of sibling manage tools.

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?

The domain-focused title and operation list give clear context for when to use this tool: when an agent needs to create or inspect occluder nodes. It does not explicitly name alternatives or exclusion conditions, but the purpose is clear enough among the many sibling tools.

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

Deploy Server