Worked prompts for production investigations, battery diagnostics, chart edits, PV reports, PDFs and custom KPI formulas.
These examples use fictitious sites. Replace names and periods with your own selections. Start each new connection with portal_guide to check the account. The assistant must obtain site IDs, asset paths, meter keys and report IDs from authorized results rather than guess them.
Include the site or portfolio, period, timezone, required units and whether you want a saved change. Ask for a distinction between measured facts, calculations and interpretation.
Use the connected Unify account. Work on Demo Solar North for the last complete calendar month in Europe/Brussels. Identify the exact start and end dates. Show production in kWh, capacity in kWp and PR in percent, with missing inputs and coverage. Do not save changes.
For a large portfolio, work in batches and ask the assistant to identify the sites it has actually checked. A first page of results is not the whole account.
List the accessible sites, following pagination. For the first ten PV sites, compare production, specific yield and PR over last month using the same period. State which values are unavailable and why. Rank only comparable results. Include site IDs and the data sources used. Do not change anything.
The assistant first discovers sites and their configuration, then requests the relevant performance data. It should separate missing readings, missing PV configuration and low measured performance. A site with no usable PR must not be silently assigned zero or placed at the bottom as the worst performer.
Verify the period and units against PV indicators. A simple average of site percentages is not automatically a valid portfolio PR; ask the assistant to explain the aggregation method.
At Demo Storage West, inspect the asset tree and identify the battery, hybrid inverter and controller. Read the available battery power, state of charge and relevant control information for yesterday. Include measurement timestamps, units and any limiting factors. Explain what the data supports and what remains unknown. Do not send commands or edit configuration.
Use actual asset paths from the tree so information from different devices is not mixed. A controller can explain a power limit while the battery itself supplies state of charge. Missing battery telemetry does not prove there is no battery.
MCP can read control diagnostics; it does not issue charge, discharge, firmware update or relay commands. Compare the result with battery readings and controller decisions.
Requires editing authorization and site dashboard editing rights.
Read Demo Storage West's existing dashboard, all pages and available meter keys. Propose one battery-power trend chart on its first page. Explain the meter, unit and period. Keep every existing chart and page unchanged. Show me the proposed change before saving it.
After checking the proposal, ask the assistant to save it. It should use the current dashboard revision and edit_chart to add the one widget. The tool preserves the other widgets and pages. If the dashboard changed meanwhile, re-read it before continuing.
Open the site in Unify, select the same dashboard page and confirm the new title, meter, unit and period. A battery power chart uses power, not cumulative energy or state of charge. You can remove or refine the chart in the portal afterwards.
For an existing chart, specify its title and the exact change:
Find the Production trend chart on the Details page. Change its title to Solar production and leave its meter selection, other options and all other widgets unchanged. Read back the saved dashboard to verify the result.
Read the current account asset dashboards and their supported definitions. Propose a last-month performance dashboard for Demo Solar North and Demo Solar South using the summary, production, PR, availability and table modules. Preserve existing dashboards. Save a new dashboard only after presenting the exact site selection and modules.
The assistant uses authorized site IDs and the account catalogue revision. Existing dashboard updates also need the dashboard's own revision. The module selection must fit Unify's supported definitions; an arbitrary image mockup is not a saved dashboard definition.
Check the result under Dashboards. See the dashboard catalogue for normal portal editing.
Requires editing authorization and report editing rights.
Find my Monthly production report in Unify Reports and read its complete definition. Propose a production chart for Demo Solar North for last month. Preserve its branding, existing sections and delivery schedule. Show the change before saving. Afterwards generate a PDF, wait for completion and retrieve the finished output. Do not email it.
The assistant must identify which supported report format it found:
| Report format | Correct workflow |
|---|---|
| Native report definition | Read with get_report, save with the current revision, start generate_report, check generation status, list completed runs and retrieve the PDF |
| Measurement or PV performance report | Find it through shared_reports, read with get_measurement_report, save with its returned revision, then render a preview or PDF |
These are two underlying formats in the unified Reports module. Do not pass one format's ID to the other tool family. A “generation started” response is not a completed PDF.
Existing delivery schedules are preserved. New reports created through these tools do not enable email delivery. Updating a report that already has a schedule can affect its next scheduled output; check the content before leaving the edit in place.
Review the PDF's period, site selection, branding, tables, chart labels and missing-data notes. See report creation.
For Demo Solar North, read the PV configuration and available measurements. Identify the inputs required for last month's PV performance report, including capacity and irradiation. List missing or inconsistent inputs without inventing replacements. If the configuration is sufficient, propose a PV performance report, show its site and period, then save and preview it after approval.
Correct inputs before relying on the resulting PR. If the assistant proposes a configuration change, require a traceable source for the new value. A connector cannot infer a validated installed capacity, sensor calibration or contractual target merely from a site name.
After rendering, compare the figures with PV performance reports. A successful PDF export does not validate the underlying measurements.
Saving requires editing authorization and account settings permission. Previewing does not save.
Read the account's KPI formulas, supported variables, defaults and revision. Propose a custom KPI for specific yield using the actual energy and capacity variables supplied by Unify. Include the unit and handling of missing inputs or zero capacity. Preserve every existing formula. Preview the complete proposed catalogue for Demo Solar North over last month and explain the result. Do not save yet.
Inspect the preview and expression. If correct, ask the assistant to save the catalogue with the current revision. A formula change is an account-level configuration change, not a private formula for one conversation. Check the result under Formulas & KPIs and verify the affected calculations with a known period.
Use only supported variables and functions returned by the tool. Do not silently replace missing irradiation with zero or remove data-quality checks to produce a percentage. To restore a built-in expression, use the default returned by get_kpi_formulas, preserving unrelated custom entries.
Add a note to Demo Storage West: “Inspected yesterday's battery data. State-of-charge readings were unavailable during the morning period; controller messages require follow-up.” Do not change alarms, actions or equipment settings.
The note is saved on the authorized site and visible to users with the relevant portal access. It does not create an email, task or alarm rule. To avoid duplicates, read existing notes when repeating a request after a timeout.
Ask it to name the failed step, tool and missing permission or input, while keeping tokens and credentials out of the answer. A proposal, successful save, generated preview and completed PDF are different outcomes. Use troubleshooting before repeating a write operation.
MCP: accounts, permissions and revocation
Understand personal Insights access, read-only and editing scopes, account binding, session expiry and revoking AI connections.
MCP: troubleshoot connections and operations
Resolve OAuth sign-in, wrong-account access, missing tools, read-only errors, conflicts and incomplete report generation.