Tool reference
SolarSENS MCP exposes read-only tools. The assistant selects a tool from your question, and every Plant read uses the access scope of the connected account.
Tool catalog
| Tool | Use it to |
|---|---|
search_plants | Find accessible Plants by name, code, or location. |
list_portfolios | List portfolios containing accessible Plants. |
get_portfolio_overview | Read date-bound portfolio performance. |
get_plant_overview | Read the current overview for one Plant. |
list_devices | List devices in a Plant. |
get_performance | Read daily or five-minute performance points. |
query_timeseries | Read selected time-series metrics. |
get_management_summary | Read actual, target, loss, availability, and coverage values when available. |
list_metrics | Discover metric names, units, and descriptions. |
query_datahub | Read selected, bounded metric values when available. |
list_alarms | Read alarm history for a Plant. |
get_alarm | Read one alarm occurrence. |
list_workorders | Read work orders for a Plant. |
get_workorder | Read one work order. |
Some tools depend on the connected account and the current backend data contract. If a capability is unavailable, the assistant should report that clearly instead of inventing a result.
Shared query rules
Date-bound tools use a complete window:
{
"start": "2026-09-01T00:00:00+08:00",
"end": "2026-09-08T00:00:00+08:00",
"timezone": "Asia/Kuala_Lumpur",
"interval": "daily"
}
startandendare ISO 8601 date-times with an offset.endmust be afterstart.timezoneis an IANA time-zone name.intervalisdailyor5min.- Daily queries cover up to 366 days.
- Five-minute queries cover up to 31 days.
- A query accepts at most 50 Plant IDs or metric names.
- Results are bounded to 1,000 rows or 1 MB of serialized data.
Use the canonical Plant ID returned by discovery for later reads. A Plant name is a search input, not an authorization method.
Response fields
Successful responses can include:
- a safe request ID;
- the Plant or other entities used by the result;
- the resolved date window and timezone;
- metric definitions when relevant; and
- coverage, warnings, and truncation metadata.
Missing values remain missing. An unavailable upstream is not reported as a successful empty result.
Read-only boundary
The MCP does not provide tools to:
- create, edit, assign, resolve, or delete work orders;
- acknowledge or clear alarms;
- change Plant, device, user, or subscription configuration;
- run arbitrary SQL, HTTP, storage, or backend requests; or
- start export jobs.
Reading a tool result never changes SolarSENS data.