What we build
Built on what KBR EnergyManagement GmbH documents: metering points, stored measured values, OBIS codes, cost centres, energy uses, machines, indicators. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# kbr-visual-energy-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
get_metering_point_sum: # metering point, OBIS, first and last date -> stored sum
backend: Excel function VE4_CalcMPointSum
mode: read
get_metering_point_status: # metering point, OBIS, first and last date -> status string
backend: Excel function VE4_GetMPointStatus
mode: read
get_cost_centre_sum: # medium, cost centre, OBIS, period -> stored sum
backend: Excel function VE4_CalcCCenterSum
mode: read
get_energy_use_sum: # medium, energy use, OBIS, period -> stored sum
backend: Excel function VE4_CalcEBenefitSum
mode: read
get_machine_sum: # medium, machine, OBIS, period -> stored sum
backend: Excel function VE4_CalcMSystemSum
mode: read
get_indicator_sum: # indicator, OBIS, first and last date -> stored sum
backend: Excel function VE4_CalcPIndicatorSum
mode: read
audit: every call logged with user, tool, arguments and the visual energy response
The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.