Tools
Every tool the DUET MCP connector offers your assistant, and what each one returns.
Your assistant chooses which tools to call based on your question. You don't need to name a tool, but the list helps you know what you can ask about, and helps your IT team review the connector.
Every tool is read-only, changes nothing in DUET, and reaches only DUET data.
Find sites and records
| Tool | Returns |
|---|---|
list_portfolios | The organizations and portfolios you can access, with how many sites each holds. |
list_projects | The sites in an organization or portfolio, with when each site's meter last reported. |
search | Sites, issues, and work orders that match a name, portfolio, key, or words in an issue or work order. |
fetch | The full record behind a search result. |
sensor_hierarchy | A site's meters, blocks, inverters, and other devices, and what each one measures. |
Performance and losses
| Tool | Returns |
|---|---|
portfolio_summary | A portfolio's daily, weekly, or monthly report: totals, losses by cause, and sites ranked by net loss. |
project_summary | A site's daily, weekly, or monthly report: expected and measured energy, PI, losses by cause, and the worst blocks. |
loss_breakdown | Expected energy, curtailment, measured energy, and PI for one or more sites, with losses broken down by cause, block, or device. |
loss_timeline | Individual loss events: which device lost energy to which cause, when, and how much. |
block_performance | Each block's PI over a time window, lowest first. |
timeseries | Measured energy, expected energy, and PI over time for any device and measure. |
timeseries_cohort | Every device of one kind compared and ranked, for example all inverters at a site. |
raw_sensor_timeseries | Sensor readings with no model, such as temperatures, frequency, and tracker position. |
availability | Time-based availability for each site, as shown in reports. |
energy_budget | Measured and expected energy against the site's budget, year, quarter, or month to date. |
power_factor | The site's power factor at the meter. |
capacity_tests | The site's capacity tests and whether each one passed. |
Batteries
| Tool | Returns |
|---|---|
battery | Energy charged and discharged, cycles, availability, and round-trip efficiency. |
battery_outages | Which battery containers were offline or derated, and for how long. |
battery_report | A battery site's daily, weekly, or monthly report, including contract availability. |
Issues and work orders
| Tool | Returns |
|---|---|
list_issues | A site's issues, with status, priority, cause, and the energy each one lost. |
get_issue | One issue in full, with its devices, linked work orders and alarms, and history. |
issue_loss_rollup | What a site's issues cost over a period, grouped by block, issue type, or cause. |
list_work_orders | A site's work orders, newest first. |
get_work_order | One work order in full, with its devices and field log. |
Data health and model inputs
| Tool | Returns |
|---|---|
data_freshness | How current each site's data is. |
data_quality | A quality score for each sensor channel, worst first. |
met_source_coverage | Days when expected energy was calculated from satellite irradiance. |
omitted_days | Days left out of reporting, with the reason. |
met_stations | The site's irradiance sensors compared with the model. |
site_design | The equipment each block is built from, with DC and AC capacity. |
model_settings | The assumptions behind expected energy, such as soiling, degradation, and power limits. |
modeled_losses | Where the model says the site's energy goes, from irradiance on the array to the grid. |
For what PI, expected energy, and the loss causes mean, see Core concepts.