Schema Discovery
Loomle discovers capability in three layers. Load only the layer needed for the current decision.
1. Resident Guide
The sal_schema MCP tool description carries the compact resident SAL guide. It explains bindings, Query, Patch, and Result Text shapes, Object Text, references, creation, and diagnostics once.
An agent does not need to request this guide before ordinary work.
2. Static Interface Cards
List the active modules:
sal_schema({})
Load one domain contract:
sal_schema({ module: "state_tree" })
A static card describes:
- target and identity rules;
- query operations and clauses;
- Result Text and Object Text relationships;
- Palette and creation rules;
- Patch operations;
- compile, save, and handoff boundaries; and
- features intentionally outside the interface.
Static cards do not load UE objects and do not describe the runtime state of one concrete asset.
3. Dynamic Exact Schema
Append the dynamic-schema clause to an exact subject:
eventGraph = target {
domain: graph,
asset: "/Game/BP_Door.BP_Door",
blueprintId: "11111111-1111-1111-1111-111111111111",
id: "22222222-2222-2222-2222-222222222222"
}
query eventGraph
@node-guid
with schema
Or inspect an exact Palette capability:
eventGraph = target {
domain: graph,
asset: "/Game/BP_Door.BP_Door",
blueprintId: "11111111-1111-1111-1111-111111111111",
id: "22222222-2222-2222-2222-222222222222"
}
query eventGraph
palette @palette-entry-id
with schema
The result reports fields, constraints, direct Patch statements, available UE operations, parameters, outputs, and copyable templates for that resolved context.
Dynamic schema is intentionally unavailable on broad summaries and ambiguous collections. First resolve an exact object or Palette entry.
Which Layer Should I Use?
| Question | Discovery layer |
|---|---|
| How does SAL generally work? | Resident guide |
| Which operations does Graph support? | Static Graph card |
| Can this exact Node add a dynamic Pin now? | Exact Node schema |
| Which Palette fields create this capability here? | Exact Palette entry |
| Which field or destination is writable? | Exact object schema |
Diagnostics Close the Loop
Useful failures should point to the next discovery action:
- unknown syntax → load the relevant static interface card;
- unknown field or operation → repeat the exact-schema query shown above;
- stale id → repeat the relevant summary, collection, or tree query;
- unavailable capability → follow the returned reason and next-query guidance.