Booking layers
These tools help you find booking layers (layer_uuid), create snapshots, and manage layer groups for reports.
Available tools
Layers & snapshots
list_layerscreate_snapshot_layers
Layer groups
list_layer_groupscreate_layer_groupdelete_layer_group
Scope
Booking layers and groups belong to companies (companyUuid). Call list_companies to choose the matching companyUuid.
List layers (list_layers)
list_companies→ choosecompanyUuidlist_layerswith an optionalcompanyUuidfilter- Note
layer_uuid,layer_type,is_default,is_forecast, andis_locked
is_default: true and layer_type not equal to snapshot (for example import, manual).
Create a snapshot (create_snapshot_layers)
Creates one new locked snapshot layer per company that has aggregated values. Values from several source layers are merged per company.
Parameters:
companyUuids— at least one companysourceLayerUuids— at least one source layer (UUIDs fromlist_layers)periodRange— optional{ from: "YYYY-MM", to: "YYYY-MM" }; omit it or passnullfor every period that has data
created_count and created_layers with layer_uuid, name, and company_uuid for each snapshot created.
Notes:
- Snapshots are always created locked and cannot be overwritten via MCP.
- If no values exist for the chosen source layers and period range, the call fails.
Layer groups
Groups are named sets oflayer_uuid members per company. Use them in resolve_report:
- Standard:
selectedLayerGroupUuids - Rolling forecast: per slice in
periodSlices[].selectedLayerGroupUuids - Comparison: per side in
compareSides.sideA/sideBasselectedLayerGroupUuids
list_layer_groups— show existing groupscreate_layer_group— new group withcompanyUuid,name, andlayerUuidsdelete_layer_group— remove the group (members remain as individual layers)
Recommended flow
list_companieslist_layers(optionally filtered bycompanyUuid)- Choose default or desired source layers as
sourceLayerUuids - Call
create_snapshot_layers list_layersagain — new entries withlayer_type: snapshotandis_locked: true- Optional: use the snapshot or a forecast layer in
resolve_report(standard, rolling forecast, or comparison — see Reports)
Typical use cases
- Freeze month-end before new imports or plan values arrive
- Keep a business plan or forecast state as a locked reference layer
- Merge several source layers (import + manual) into one snapshot